Skip to main content
Glama

ADS Beast

report_create

Save a report for a client. With content: stores that text (Markdown). Without content: generates a 30-day campaign summary. AI: 1 AI request.

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": {
      "client_id": "<client_id>"
    },
    "name": "report_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoShort title.
contentNoFull report text in Markdown.
client_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the description's added value is the implicit side effect: omitting content triggers a 30-day campaign summary generation, plus the cost disclosure "AI: 1 AI request." That cost/quota signal is genuinely useful context an agent cannot get from structured fields. It stops short of saying whether an existing report is overwritten or whether generated content can be reviewed before saving.

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

Conciseness4/5

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

Three short clauses, front-loaded with the core action, with zero filler. The telegraphic fragments ("AI: 1 AI request.") read like shorthand rather than prose, but each fragment carries distinct information.

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

Completeness3/5

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

With no output schema, the description never says what is returned (a report ID, the generated text, a confirmation), which matters when the no-content mode produces generated material. It also leaves the create-vs-overwrite question and the AI cost's practical implications unstated for a tool flagged openWorldHint.

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

Parameters4/5

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

Schema coverage is 67% and client_id has no description at all, but the description compensates by explaining the semantics of content (Markdown text, and its presence/absence changes tool behavior entirely) — the single most important thing to know about this schema. It adds nothing about client_id, so the gap is only partially closed.

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 first sentence gives a specific verb and resource ("Save a report for a client"), and the following clauses distinguish the two operating modes. It does not differentiate itself from siblings such as seo_performance_report, creative_fatigue_report, or prepare_client_report_send, so an agent must infer which report tool to pick.

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?

"With content: ... Without content: ..." effectively tells the agent which mode applies based on whether it supplies the content parameter, which is real branch guidance. However, there is no when-to-use versus the other report-producing siblings, no prerequisites, and no statement of when a generated summary is preferable to writing one.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.