Crawlora MCP

tiktok_top_ads_analysis

Read-only

Fetch the performance chart and percentile for a Top Ads material, metric, and period. Use tiktok_top_ads_detail first when you need to inspect the creative; tiktok_top_ads_recommend and tiktok_top_ads_suggestions are discovery paths, not performance analysis.

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": {
      "material_id": "<material_id>"
    },
    "name": "tiktok_top_ads_analysis"
  }
}

Input Schema

Name	Required	Description
`metric`	No	Analysis metric, default retain_ctr. Allowed values: retain_ctr (CTR), retain_cvr (CVR), click_cnt (Clicks), convert_cnt (Conversion), play_retain_cnt (Remain).
`material_id`	Yes	Required. Top Ads material id.
`period_type`	No	Percentile lookback period in days, default 7. Allowed values: 7, 30, 180.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 5, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds scope behavior beyond that by clarifying the output (performance chart plus percentile) and framing recommend/suggestions as non-analytical discovery paths. It does not add auth or rate-limit detail, but for a read-only analytics call the added context is solid.

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 sentences, front-loaded with the primary action, followed by the disambiguation guidance. No filler; every clause carries routing or scope information.

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

Completeness5/5

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

With a full output schema, complete parameter documentation, and annotations covering safety, the only job left is purpose and sibling routing, both of which are handled. Nothing an agent needs to invoke it correctly is missing.

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%, with defaults and allowed values fully documented for metric and period_type. The description only echoes 'material, metric, and period' without adding format or constraint meaning beyond the schema, so baseline 3 applies.

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

Purpose5/5

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

States a specific verb and resource: 'Fetch the performance chart and percentile for a Top Ads material, metric, and period.' It also explicitly distinguishes itself from three named siblings, so an agent can separate it from detail/recommend/suggestions without opening schemas.

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

Usage Guidelines5/5

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

Gives explicit routing: use tiktok_top_ads_detail first to inspect the creative, and warns that recommend/suggestions are discovery paths, not performance analysis. This tells the agent when this tool is appropriate and when a sibling is the better fit.

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

All Crawlora MCP 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?