Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

snapchat_profile

Fetch a public Snapchat profile by username to get bio, subscriber count, related accounts, and Spotlight video engagement metrics.

Instructions

snapchat: User Profile. GET /v1/snapchat/profile. Get a public Snapchat profile (1 credit): name, bio, subscriber count, related accounts and the profile's Spotlight videos with views, shares and comments. Personal accounts return only username, display name and snapcode. Highlights are empty: the public page no longer embeds them. Costs 1 credit when it succeeds. Errors, blocked or timed-out requests, invalid requests and cache hits cost nothing. A not-found or empty result is charged only where that operation's published cost says so.

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>"
    },
    "name": "snapchat_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
handleYesSnapchat username

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does substantial work: it prices the call (1 credit), defines exactly when charges do and do not apply (failures, blocked, timeouts, invalid requests, cache hits), and discloses degraded-result cases (personal accounts, empty Highlights). It stops short of stating whether an API key/auth or rate limiting applies, so it is very good but not exhaustive.

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?

Front-loaded with the resource, endpoint and returned fields, then the credit/edge-case caveats. The final billing sentence is long and slightly repetitive with the preceding cost sentence, but every part still carries decision-relevant information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter read tool with no output schema and no annotations, the description supplies returned fields, degraded-result semantics, the known empty-Highlights behavior, and the full cost model. An agent has everything needed to decide whether to call it and how to interpret an empty or partial response.

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?

Only one parameter exists and the schema already documents it at 100% coverage with an example value ('teamsnapchat'), so the baseline of 3 applies. The description reinforces that the target must be a public Snapchat username but adds no format or normalization guidance beyond the schema.

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?

Names a specific verb and resource ('Get a public Snapchat profile') and enumerates the concrete fields returned: name, bio, subscriber count, related accounts, Spotlight videos with views/shares/comments. The Snapchat scoping makes it unambiguously distinct from the facebook_profile/instagram_profile siblings without needing to name them.

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?

Usage is implied by the required handle parameter and the 'public profile' framing, and the description usefully notes that personal accounts return only username/display name/snapcode. However, it never states when an agent should pick this over an alternative route, nor any prerequisites for calling it.

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