feat: Add outputSchema to report-problem and get-actor-log - #1175
Merged
Conversation
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
RobertCrupa
approved these changes
Jul 29, 2026
RobertCrupa
left a comment
Contributor
There was a problem hiding this comment.
Thank you for resolving this!
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Closes #1159, Closes #1160.
report-problemandget-actor-logwere the last helper tools with nooutputSchema, sostructuredContent-consuming clients got nothing machine-readable back, and the stateless server's result projection has no schema to project against.What changed
report-problemnow returnsstructuredContent: { reported: true }.get-actor-lognow returnsstructuredContent: { 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 livemcpcprobe caught this after the first fix attempt). It now returns exactly N.lines:=0documented as returning the entire log (existing behavior, not new — just previously unstated).apify-mcp-server-internal:structuredContentis new on both tools'tools/listentries, andget-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
Generated by Claude Code