Skip to main content
Glama
Sign In
paid-media-mcp

paid-media-mcp

by kenlim5656
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

build_performance_report

Generate a narrative performance report for campaigns or teams by combining live data with a reporting template.

Instructions

Generate a narrative performance report for a campaign or team, combining live performance data with the appropriate reporting template. Best used with a reporting template ID to match the intended audience format.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "target_type": "<target_type>",
      "target_id": "<target_id>",
      "date_from": "<date_from>",
      "date_to": "<date_to>"
    },
    "name": "build_performance_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
date_toYesReport end date (YYYY-MM-DD)
date_fromYesReport start date (YYYY-MM-DD)
target_idYesCampaign ID or team ID
target_typeYes
template_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.2/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, and the description does not disclose whether the tool mutates any data, requires specific permissions, or handles missing template_id. It only implies a read-like operation but lacks behavioral detail.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two concise, front-loaded sentences with no extraneous information. Every sentence adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and 5 parameters, the description is too sparse. It does not explain the output format, behavior when template_id is omitted, or how it differs from similar report tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 60%, but only date parameters have descriptions. The description adds context for target_type (campaign/team) and template_id (reporting template), but does not fully compensate for undocumented parameters like target_id.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool generates a narrative report for a campaign or team, combining live data with a template. This distinguishes it from sibling tools that only retrieve raw performance data.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It suggests using a reporting template ID for the intended audience, but does not explicitly state when to use this tool versus alternatives like get_campaign_performance_report or get_team_performance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools