You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(langsmith,jira,linkedin): correct claims and coercion, align block outputs
The feedback description told the model the official SDK omits session_id.
It does not -- it warns, and raises on SmithDB-only deployments. LangSmith
documents the field as required while only 'key' sits in the OpenAPI
required array; both halves are now stated.
parseLangsmithFeedbackValue was applied in the block and again in
request.body, and it is not idempotent: a quoted "1" became a number and a
quoted "null" dropped the field. The tool body covers every path including
Copilot, so the block call is removed.
Jira declared commentBody and newStatus, which no tool emits, while the
real keys were undeclared; status and assignee are objects declared as
string. LinkedIn's postUrl doc named a URN family the regex never checks.
'UUID of the tracing project (session) the feedback belongs to. Optional — LangSmith accepts feedback without it',
478
+
"UUID of the tracing project (session) the feedback belongs to. LangSmith documents it as required and its SDK warns (or errors, on SmithDB-only deployments) without it. Left optional here so blocks saved against deployments that still resolve the run server-side keep working.",
'UUID of the tracing project (session) the feedback belongs to. Optional — in the LangSmith OpenAPI spec only `key` is required by POST /api/v1/feedback, and the official SDK sends feedback without a session_id. Supply it when you have it: some LangSmith deployments cannot locate the run without it. Never guess it — use the sessionId reported by a preceding langsmith_get_run for the same run, or look the project up with GET /api/v1/sessions.',
41
+
'UUID of the tracing project (session) the feedback belongs to. LangSmith documents this as required: "POST /api/v1/feedback now requires a session_id field in the request body. It was previously optional." The official SDK warns when it is omitted and raises outright on SmithDB-only deployments, because some LangSmith deployments cannot locate the run without it. Only `key` is in the endpoint\'s OpenAPI required array, so omitting session_id will not fail request validation — but always supply it when you have it. Never guess it — use the sessionId reported by a preceding langsmith_get_run for the same run, or look the project up with GET /api/v1/sessions.',
'The `urn:li:ugcPost:` URN of the created post, read from the `x-restli-id` response header. Absent when LinkedIn omits that header.',
179
+
'The URN of the created post, read from the `x-restli-id` response header, which LinkedIn documents as carrying the ugcPost id. Reported as received. Absent when LinkedIn omits that header.',
180
180
optional: true,
181
181
},
182
182
postUrl: {
183
183
type: 'string',
184
184
description:
185
-
'LinkedIn URL of the created post. Viewable by an authorized LinkedIn member — not a guaranteed public permalink. Absent when the `x-restli-id` header was missing or did not carry a `urn:li:` URN of the ugcPost family.',
185
+
'LinkedIn URL of the created post. Viewable by an authorized LinkedIn member — not a guaranteed public permalink. Absent when the `x-restli-id` header was missing or did not carry a `urn:li:<entityType>:<id>` URN.',
0 commit comments