Lists saved Campaign Manager 360 report definitions visible to a profile, helping you discover available reports without executing them.
List saved CM360 report definitions visible to this profile. Does not execute reports.
| Name | Required | Description | Default |
|---|---|---|---|
| scope | No | MINE | |
| account | No | ||
| page_size | No | ||
| page_token | No | ||
| profile_id | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds the valuable clarification that this returns definitions only and does not run reports, but says nothing about pagination behavior or what 'visible to this profile' means in terms of permissions.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short sentences, front-loaded with the core action and immediately followed by the key constraint. No filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return values need no explanation. However, for a 5-parameter tool with 0% schema coverage and paginated listing semantics, the description omits how to page or how the scope/account filters interact with profile visibility.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0% across 5 parameters. The description hints at profile scoping via 'this profile' but never explains the scope enum (MINE vs ALL), the account filter, or how page_size/page_token drive pagination. With no schema documentation, this leaves most parameters opaque.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Specific verb+resource: 'List saved CM360 report definitions'. The qualifier 'visible to this profile' adds scope, and 'definitions' implicitly separates it from list_cm360_report_files. It stops short of naming the sibling that handles generated files, so an agent must infer the boundary.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
'Does not execute reports' gives a useful negative boundary, but it names no alternative for actually running or retrieving report output (e.g., list_cm360_report_files). Usage is implied rather than routed.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.