Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Snapchat profile

snapchat_profile_get
Read-onlyIdempotent

Look up a public Snapchat profile by username to retrieve account details and public information.

Instructions

Get a public Snapchat profile by handle. Requires handle.

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

Input Schema

NameRequiredDescriptionDefault
handleYesRequired. Snapchat username to look up, with or without a leading @.
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
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 the safety profile is fully covered without description help. The description adds one real behavioral detail beyond them: it only works for *public* profiles, which changes what an agent should expect for private accounts. It says nothing about failure modes for missing accounts or rate limits, keeping it at a solid 3.

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 padding. The second sentence largely restates the schema's required-field list, so it earns only partial credit rather than being fully load-bearing.

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?

For a simple read-only lookup with full schema coverage and annotations carrying the safety profile, the description covers what an agent needs to invoke it correctly. The remaining gap is what happens when the profile doesn't exist or is private, which the "public" qualifier only partly addresses.

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 every parameter, including @-prefix handling for `handle`, is already documented, warranting the baseline 3. "Requires `handle`" adds nothing the schema lacks and omits that `context` and `llm_model` are also required, which slightly understates the true required set.

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 public Snapchat profile by handle"), which is enough to distinguish it from sibling *search*/engagement tools by resource scope. It does not explicitly contrast itself with other Snapchat siblings like snapchat_spotlight_get, but the platform-plus-resource naming makes the distinction inferable.

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

Usage Guidelines2/5

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

The only usage-like statement is "Requires `handle`," which is parameter information rather than guidance on when to choose this tool. There is no mention of when to prefer it over other profile or platform tools, no exclusions, and no note about whether private/nonexistent accounts are handled differently.

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