Taseli

What stands out on TikTok in the field

get_market_trends

Read-onlyIdempotent

The standout TikTok ads in Israel in the business's category over the last 30 days (TikTok Creative Center), ranked: title, objective and cover. These are category trends, not the business's competitors (TikTok's ad library doesn't cover Israel). Useful for 'what works on TikTok in my field?'.

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_market_trends"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	How many (default 10).
`language`	No	Answer language. The business's language by default.

Output Schema

Name	Required	Description
`note`	No	A plain note instead of data (nothing connected yet, not available here).
`error`	No	Why nothing was done, as a short code.
`truncated`	No
`truncatedNote`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 3, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds real value beyond them: data source (TikTok Creative Center), a fixed 30-day window, geographic limitation to Israel, and the reason the scope is category-level rather than competitor-level.

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?

The core scope and data source are front-loaded in one dense sentence, followed by the important competitor caveat. Slightly cluttered by parentheticals and a closing use-case line that largely restates the title, but nothing is genuinely wasteful.

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?

An output schema exists, so return-value detail needn't be in the description. With only two optional, fully documented parameters and a low-complexity read operation, the description covers everything an agent needs to select and call it correctly.

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%, so both limit (1-20, default 10) and language (he/ar/en, defaults to business language) are already documented. The description adds no formatting or behavioral detail about these parameters, so the 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 resource (standout TikTok ads in the business's category), scope (Israel, last 30 days, TikTok Creative Center), and return contents (title, objective, cover, ranked). It explicitly separates itself from get_competitor_ads by saying these are category trends, not the business's competitors.

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

Usage Guidelines4/5

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

Gives a clear use case ("what works on TikTok in my field?") and an explicit exclusion (not competitor tracking, because TikTok's ad library doesn't cover Israel). It stops short of naming the sibling tool an agent should call instead for competitor ads, leaving that routing to inference.

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?