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: 2f22a43

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]

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.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch mcp-fix-trace

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 9fdf91a and 2f22a43.

📒 Files selected for processing (3)

• .changeset/fuzzy-wolves-repeat.md (1 hunks)
• packages/cli-v3/src/mcp/formatters.ts (1 hunks)
• packages/core/src/v3/schemas/api.ts (1 hunks)

🧰 Additional context used

📓 Path-based instructions (2)

**/*.{ts,tsx}

📄 CodeRabbit inference engine (.github/copilot-instructions.md)

**/*.{ts,tsx}: Always prefer using isomorphic code like fetch, ReadableStream, etc. instead of Node.js specific code
For TypeScript, we usually use types over interfaces
Avoid enums
No default exports, use function declarations

Files:

• packages/core/src/v3/schemas/api.ts
• packages/cli-v3/src/mcp/formatters.ts

{packages/core,apps/webapp}/**/*.{ts,tsx}

📄 CodeRabbit inference engine (.github/copilot-instructions.md)

We use zod a lot in packages/core and in the webapp

Files:

• packages/core/src/v3/schemas/api.ts

🧬 Code graph analysis (1)

packages/cli-v3/src/mcp/formatters.ts (1)

apps/webapp/app/v3/eventRepository/clickhouseEventRepository.server.ts (1)

• span (1703-1720)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (23)

• GitHub Check: units / webapp / 🧪 Unit Tests: Webapp (5, 8)
• GitHub Check: units / webapp / 🧪 Unit Tests: Webapp (7, 8)
• GitHub Check: units / webapp / 🧪 Unit Tests: Webapp (6, 8)
• GitHub Check: units / webapp / 🧪 Unit Tests: Webapp (8, 8)
• GitHub Check: units / internal / 🧪 Unit Tests: Internal (7, 8)
• GitHub Check: units / webapp / 🧪 Unit Tests: Webapp (4, 8)
• GitHub Check: units / webapp / 🧪 Unit Tests: Webapp (3, 8)
• GitHub Check: units / webapp / 🧪 Unit Tests: Webapp (1, 8)
• GitHub Check: units / webapp / 🧪 Unit Tests: Webapp (2, 8)
• GitHub Check: units / internal / 🧪 Unit Tests: Internal (8, 8)
• GitHub Check: units / packages / 🧪 Unit Tests: Packages (1, 1)
• GitHub Check: units / internal / 🧪 Unit Tests: Internal (5, 8)
• GitHub Check: units / internal / 🧪 Unit Tests: Internal (3, 8)
• GitHub Check: units / internal / 🧪 Unit Tests: Internal (4, 8)
• GitHub Check: units / internal / 🧪 Unit Tests: Internal (1, 8)
• GitHub Check: units / internal / 🧪 Unit Tests: Internal (6, 8)
• GitHub Check: e2e / 🧪 CLI v3 tests (windows-latest - npm)
• GitHub Check: units / internal / 🧪 Unit Tests: Internal (2, 8)
• GitHub Check: e2e / 🧪 CLI v3 tests (ubuntu-latest - npm)
• GitHub Check: e2e / 🧪 CLI v3 tests (windows-latest - pnpm)
• GitHub Check: e2e / 🧪 CLI v3 tests (ubuntu-latest - pnpm)
• GitHub Check: typecheck / typecheck
• GitHub Check: Analyze (javascript-typescript)

🔇 Additional comments (2)

.changeset/fuzzy-wolves-repeat.md (1)

1-5: LGTM!

The changeset correctly documents this as a patch-level fix with a clear description.

packages/cli-v3/src/mcp/formatters.ts (1)

241-241: Correct adaptation to the schema change.

The formatter now correctly accesses span.data.message instead of span.message, aligning with the restructured RetrieveRunTraceSpanSchema.

---

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.}