WhichPost

Latest campaign report

get_latest_report

Read-onlyIdempotent

The headline answer of the newest report, or of the one named by report_id: paying users from creator posts with their likely range, spend, cost per paying user with its range against the founder's target, revenue so far from those paying users after refunds (with its range, per 1,000 views and against spend) when the sales data has payment amounts, how many creators to rebook, test again or pause, whether the posts show a clear effect yet, free trials still running, whether the report's checks on the founder's own history are done, and the report link.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_latest_report"
  }
}

Input Schema

Name	Required	Description	Default
`report_id`	No	A report id from list_campaigns. Leave out for the newest report.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 14, 2026

TDQS

B3.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds genuinely non-obvious behavior: revenue-after-refunds figures appear only 'when the sales data has payment amounts', and it discloses conditional fields like whether the report's history checks are done. It still says nothing about freshness, caching, or error behavior for a bad report_id.

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

Conciseness2/5

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

The purpose is front-loaded, but the whole description is a single run-on sentence enumerating every returned metric — content already fully specified by the output schema. This enumeration crowds out routing information (when to use this vs. siblings) and makes the definition harder to scan.

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?

All structured fields (annotations, 100%-covered single param, output schema) are present, so the definition is functionally complete for invocation. The description's effort is misallocated to restating return values that the output schema already carries, while selection criteria versus siblings remain unaddressed.

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 description coverage is 100% for the single report_id parameter, so the baseline is 3. The description mirrors the schema ('the one named by report_id') without adding format, provenance, or failure-mode detail beyond the existing pattern constraint and 'from list_campaigns' hint.

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 states the specific resource returned (the newest report, or the one named by report_id) and enumerates its headline contents, so an agent knows what it retrieves. It does not, however, distinguish itself from lookalike siblings such as get_sample_report, refresh_report, or list_campaigns, which an agent would need to route between.

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?

Usage is only implied: 'the newest report, or of the one named by report_id' plus the schema note 'Leave out for the newest report' tells the agent how the default behaves, but there is no explicit when-to-use-this vs. get_sample_report/refresh_report guidance and no stated prerequisites.

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

All WhichPost tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?