Skip to main content
Glama
Sign In

sonar

by app.trysonar
OverviewDiscussionsAdmin

Competitor TikTok Videos

sonar_ad_spy_tiktok_posts
Read-onlyIdempotent

A linked TikTok account's cached public videos with real counters (views, likes, comments, shares, saves), caption, post date and a breakout flag (3× or more the account's median views). Use url (permanent); compact by default, so the expiring cover_url is left out (fields: "full" adds it). Cached read; sonar_ad_spy_refresh with kind "tiktok" fetches newer videos. Requires an Indie or Agency plan (a trial counts).

Input Schema

NameRequiredDescriptionDefault
sortNoOrder (default most viewed).
limitNoVideos to return (1-200, default 50).
fieldsNo"compact" (default): each video without its expiring `cover_url`; the permanent `url`, caption, dates and every counter stay. "full": adds `cover_url` (an expiring CDN image link).compact
account_idYesSonar id of a linked TikTok account (`account_id` from sonar_ad_spy_competitors).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / fields
      Added value: +{
+  "default": "compact",
+  "description": "\"compact\" (default): each video without its expiring `cover_url`; the permanent `url`, caption, dates and every counter stay. \"full\": adds `cover_url` (an expiring CDN image link).",
+  "enum": [
+    "compact",
+    "full"
+  ],
+  "type": "string"
+}
  2. Added

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations it discloses non-obvious traits: results are cached (so potentially stale), newer data requires a separate refresh call, `cover_url` expires while `url` is permanent, and access is gated to Indie/Agency plans. It also defines the derived `breakout` flag (≥3× the account's median views), which is behavioral meaning an agent could not infer from annotations.

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 sentences, front-loaded with what is returned, then the compact/full trade-off, then freshness and plan gating. Dense and mostly waste-free, though the parenthetical counter list and the `breakout` definition make the first sentence long.

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 no output schema, the description carries the return-value burden and does so well: field list, the breakout flag, and the compact/full difference including which URL is durable. It covers caching, refresh, and plan gating. What it omits is pagination/truncation behavior beyond `limit` and the shape of the response envelope.

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 already 100%, so baseline is 3. The description still adds value by explaining the consequence of `fields`: compact omits the expiring `cover_url` but keeps the permanent `url`, caption, dates and all counters. It does not discuss `sort` or `limit` beyond the schema, so it earns only a modest lift over baseline.

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?

Opens with a precise verb+resource+scope: 'A linked TikTok account's cached public videos with real counters (views, likes, comments, shares, saves), caption, post date and a `breakout` flag'. It names the sibling that does the adjacent job (sonar_ad_spy_refresh) and clarifies the cached-vs-live distinction, so an agent can separate it from refresh without reading either schema.

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 explicit routing advice: 'Cached read; sonar_ad_spy_refresh with kind "tiktok" fetches newer videos', which tells the agent when to pick the alternative. It also states the plan prerequisite (Indie/Agency, trial counts). It stops short of saying when NOT to use this tool at all (e.g. for non-TikTok platforms or unlinked accounts), so it is strong but not exhaustive.

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

All sonar toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources