Fix for the MCP tool that gets logs for debugging runs

[matt-aitken]

This was broken when we changed the data on the backend that returns
log/span data from runs. We changed the data structured and the internal
API that the MCP client uses was failing to parse with the Zod schema

[changeset-bot]

🦋 Changeset detected

Latest commit: 1684b23

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 23 packages

Name	Type
trigger.dev	Patch
d3-chat	Patch
references-d3-openai-agents	Patch
references-nextjs-realtime	Patch
@trigger.dev/build	Patch
@trigger.dev/core	Patch
@trigger.dev/python	Patch
@trigger.dev/react-hooks	Patch
@trigger.dev/redis-worker	Patch
@trigger.dev/rsc	Patch
@trigger.dev/schema-to-json	Patch
@trigger.dev/sdk	Patch
@trigger.dev/database	Patch
@trigger.dev/otlp-importer	Patch
@internal/cache	Patch
@internal/clickhouse	Patch
@internal/redis	Patch
@internal/replication	Patch
@internal/run-engine	Patch
@internal/schedule-engine	Patch
@internal/testcontainers	Patch
@internal/tracing	Patch
@internal/zod-worker	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[coderabbitai]

Caution

Review failed

The head commit changed during the review from 86eca83 to 1684b23.

Walkthrough

This PR introduces a bug fix for the MCP tool's run log retrieval functionality. The changes include: (1) a new changeset documenting a patch for the MCP tool's run log retrieval, (2) schema field restructuring in RetrieveRunTraceSpanSchema that moves the message field from top-level to nested data object and runId from nested to top-level, and (3) a formatter update in the CLI that adjusts span message display to reference the field's new location in the nested data object.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

• Verify that the schema field reorganization (RetrieveRunTraceSpanSchema) is correctly reflected across all consuming code beyond the formatter update
• Confirm that the removal of environmentType from the schema's nested data object does not impact other parts of the system that may depend on this field
• Ensure the formatter change in span.data.message is the only place in the codebase that needed updating to align with the new schema structure

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description explains the bug and root cause but lacks required sections from the template including Testing, Changelog, Checklist completion, and issue reference.	Add missing template sections: checklist confirmation, issue number (Closes #), Testing section with reproduction steps, and Changelog with brief change summary.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main fix: addressing a broken MCP tool for retrieving run logs, which aligns with the core changes in the PR.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}