Taseli

Make a results report

make_report

Writes a results report, the same as Reports in Taseli: the last 28 complete days (the app's window) or the last full month, for the owner or written for the business's client (no budget or bid talk), from Taseli's records: results by week and campaign, what Taseli did and why, what comes next in the plan, the creatives, what it learned. Saved as a draft in Taseli; share also makes a private read-only link. Takes up to a minute and uses Taseli's AI; changes nothing in any account.

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": "make_report"
  }
}

Input Schema

Name	Required	Description
`range`	No	28d (default: the last 28 complete days) or the last full calendar month.
`share`	No	true: also make the private read-only link to send someone.
`audience`	No	owner (default) or written for the business's client (agencies).
`language`	No	Answer language. The business's language by default.

Output Schema

Name	Required	Description	Default
`to`	No
`url`	No
`from`	No
`error`	No
`summary`	No
`headline`	No
`reportId`	No
`shareUrl`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 3, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Goes well past the annotations: discloses that it takes up to a minute, uses Taseli's AI, persists a draft in Taseli, and that share creates a private read-only link. It also resolves the ambiguity of readOnlyHint=false by stating it "changes nothing in any account" — useful given non-idempotent, non-read-only hints. Loses a point for not saying whether repeat calls create duplicate drafts.

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?

Front-loads verb and resource, then the range/audience variants, then side effects and latency — a sensible order. The middle colon-list of report sections is somewhat sprawling and could be tightened, but each clause carries information an agent would otherwise have to guess.

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

Completeness4/5

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

With an output schema present, return shape needn't be explained, and the description still covers defaults, latency, persistence, and sharing. The remaining gap is relational: it doesn't say how the produced draft relates to list_reports or how it differs from what_we_did, which matters in this crowded sibling set.

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 100%, so baseline is 3, but the description adds real meaning: it explains the 28-day window as the app's default unit, contrasts it with a full month, and specifies that the client audience version omits budget and bid talk — editorial semantics the enum alone cannot convey.

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?

Opens with a specific verb+resource ("Writes a results report") and immediately anchors it to a known artifact ("the same as Reports in Taseli"), then enumerates the report's sections. It clearly differs from data-fetch siblings like get_results or list_reports, though it never names those siblings to sharpen the boundary.

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 implied rather than stated: an agent can infer "call this when the user wants a shareable results report," and the audience/range/share params sketch the situations. There is no explicit when-not guidance or routing to get_results (raw numbers) or list_reports (existing reports), which are the obvious alternatives in the sibling set.

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

All Taseli 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?