Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Snapchat Spotlight comments

snapchat_spotlight_comments_list
Read-onlyIdempotent

Retrieve top-level comments from a Snapchat Spotlight video by URL, using a cursor to page through additional comments.

Instructions

List top-level comments on a Snapchat Spotlight video. Requires url. Returns a list (use cursor when paginated).

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

Input Schema

NameRequiredDescriptionDefault
urlYesRequired. Link to the Snapchat Spotlight video.
cursorNoPagination cursor from page.nextCursor of a previous response.
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 readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered structurally. The description adds the pagination behavior and the url prerequisite, but says nothing about rate limits, auth, or what a returned comment 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 with the purpose front-loaded and no wasted wording. It is terse to the point of thinness but every sentence carries information.

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?

For a simple read-only list call with full schema coverage and rich annotations, the definition is adequate. With no output schema, though, it should say more about what a comment record includes or how many are returned per page.

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 url, cursor, context, llm_model and conversation_id are all already documented. The description merely echoes the url and cursor semantics, adding no meaning beyond the schema; baseline 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?

Uses a specific verb+resource ('List top-level comments on a Snapchat Spotlight video') and the word 'top-level' implicitly scopes it away from reply-listing tools. It falls short of a 5 only because it never names the alternative tool an agent should pick for replies.

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?

It states the prerequisite ('Requires `url`') and gives a pagination hint ('use cursor when paginated'), which is real usage guidance. There is no explicit when-to-use/when-not or pointer to sibling comment tools, so guidance remains implied.

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