Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Snapchat Spotlight

snapchat_spotlight_get
Read-onlyIdempotent

Retrieve a Snapchat Spotlight video by URL to access the video for review, analysis, or processing.

Instructions

Get a Snapchat Spotlight video by URL. Requires 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": {
      "url": "<url>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "snapchat_spotlight_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesRequired. Link to the Snapchat Spotlight video.
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.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true and destructiveHint=false, so the safety and idempotency profile is fully covered structurally. The description adds no behavior beyond that — it does not mention that the call reaches the open web, what happens with an invalid or private URL, or what the response contains.

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, front-loaded with the action and resource, with no filler. The second sentence ("Requires `url`.") is redundant with the schema's required list and its own parameter description, which keeps it from a 5.

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?

This is a simple single-resource read tool with a fully described schema and complete annotations, so the description need not carry much. However, there is no output schema, and the description says nothing about what a Spotlight fetch returns (video metadata, author, metrics), leaving a real gap for the calling agent.

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% and all four parameters (url, context, llm_model, conversation_id) are documented in the schema itself. The description only restates that url is required, adding no meaning beyond the schema, so the baseline of 3 applies.

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 ("Get a Snapchat Spotlight video") and the lookup key ("by URL"), which is enough to distinguish it from snapchat_spotlight_comments_list and the profile/appleMusic siblings. It stops short of explicitly naming a sibling it is not, so it lands at 4 rather than 5.

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?

"By URL" implies the precondition that the caller already holds a Spotlight link, which is implicit usage guidance. There is no explicit when-to-use/when-not statement and no reference to alternatives such as the comments-list sibling for related data.

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