Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get TikTok Ad Library ad

tiktok_adLibrary_ad_get
Read-onlyIdempotent

Fetch a single TikTok Ad Library or Top Ads creative by ad ID or public URL to view one ad's details.

Instructions

Get a single TikTok Ad Library or Top Ads creative by ad id or public ad URL. Optional inputs: adId and url.

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": {
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "tiktok_adLibrary_ad_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoPublic TikTok Ad Library or Top Ads detail URL for the ad.
adIdNoTikTok Ad Library or Top Ads ad id.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. What the description omits is the important behavioral detail that the schema lists both `adId` and `url` as optional, even though the tool requires at least one, and it never says which takes precedence when both are passed. It also says nothing about failure behavior for an invalid or private URL.

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?

Two short sentences with the core action front-loaded and no filler. The second sentence largely duplicates the schema's parameter list, which is the only wasted clause.

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?

With five parameters, full schema coverage and no output schema, the definition covers the mechanics but leaves gaps: it does not describe the shape of the returned creative, and it does not resolve the at-least-one-of `adId`/`url` requirement that an agent must infer from two optional fields.

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 identifier parameters are fully documented in the schema and a baseline of 3 applies. The description simply restates that they are optional and adds no precedence or format guidance beyond what the schema already provides.

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?

States a specific verb and resource: fetch one TikTok Ad Library or Top Ads creative, identified by ad id or public URL. The word "single" implicitly contrasts with the sibling search tool, though the sibling is never named, so differentiation is left to inference.

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?

The description implies usage (retrieve details for one known ad via id or URL) but never says when to prefer this over tiktok_adLibrary_ads_search_get or the other platform ad-get tools. No prerequisites, no explicit exclusions.

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

Deploy Server

Other Tools