Skip to content

feat: Add outputSchema to report-problem and get-actor-log - #1175

Merged
jirispilka merged 1 commit into
masterfrom
claude/apify-output-schema-report-xohw6m
Jul 31, 2026
Merged

feat: Add outputSchema to report-problem and get-actor-log#1175
jirispilka merged 1 commit into
masterfrom
claude/apify-output-schema-report-xohw6m

Conversation

@jirispilka

@jirispilka jirispilka commented Jul 28, 2026

Copy link
Copy Markdown
Collaborator

Why

Closes #1159, Closes #1160. report-problem and get-actor-log were the last helper tools with no outputSchema, so structuredContent-consuming clients got nothing machine-readable back, and the stateless server's result projection has no schema to project against.

What changed

  • report-problem now returns structuredContent: { reported: true }.
  • get-actor-log now returns structuredContent: { log: <text> }, and fixes a pre-existing off-by-one in its line-tail slice: it used to return N+1 lines when N were requested (and, against real Apify run logs which end with a trailing newline, N-1 — a live mcpc probe caught this after the first fix attempt). It now returns exactly N.
  • lines:=0 documented as returning the entire log (existing behavior, not new — just previously unstated).
  • Any impact on apify-mcp-server-internal: structuredContent is new on both tools' tools/list entries, and get-actor-log's output text is one line shorter than before. Additive/low-risk, but the internal contract suite likely needs a matching test case for both.

Notes for reviewers (human-written)

Proof it works

image

Generated by Claude Code

report-problem and get-actor-log were the last two helper tools with no
outputSchema, so clients that consume structuredContent got nothing
machine-readable back, and the stateless server's result projection had no
schema to project against.

- report-problem now returns structuredContent: { reported: true }.
- get-actor-log now returns structuredContent: { log: <text> }, and fixes a
  pre-existing off-by-one in its line-tail slice: it used to return N+1 lines
  when N were requested (and, against real Apify run logs which end with a
  trailing newline, N-1). It now returns exactly N.
- lines:=0 documented as returning the entire log (existing behavior, not
  new).

apify-mcp-server-internal's contract suite may need a matching test for the
new structuredContent on these two tools and for the get-actor-log
line-count fix.

Closes #1159, Closes #1160

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GaQ7VgYvm3m865aY4HEWbE
@github-actions github-actions Bot added t-ai Issues owned by the AI team. tested Temporary label used only programatically for some analytics. labels Jul 28, 2026
@jirispilka
jirispilka requested a review from RobertCrupa July 28, 2026 20:00

@RobertCrupa RobertCrupa left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for resolving this!

@jirispilka
jirispilka merged commit 21bb370 into master Jul 31, 2026
12 checks passed
@jirispilka
jirispilka deleted the claude/apify-output-schema-report-xohw6m branch July 31, 2026 10:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

t-ai Issues owned by the AI team. tested Temporary label used only programatically for some analytics.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

feat: Add outputSchema to get-actor-run-log feat: Add outputSchema to report-problem

4 participants