Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

instagram_profile

Fetch a public Instagram profile as a signed-out visitor sees it: bio, links, exact follower and following counts, verification, avatar and the first 12 grid posts. Cached responses cost no credits.

Instructions

instagram: Profile. GET /v1/instagram/profile. Get a public Instagram profile as a signed-out visitor sees it, in the web_profile_info shape under data.user: id, fbid, username, full name, biography, bio links, exact follower and following counts, verification, profile picture, and the profile grid's first 12 posts (edge_owner_to_timeline_media.edges). edge_owner_to_timeline_media.count is exact when Instagram shows the full number and null when it shows a rounde 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": "instagram_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
trimNoSet to true for a trimmed response.
handleYesThe Instagram username, with or without @
cache_max_ageNoUse a cached response this old or newer for 0 credits. If none is available, fetch live at the endpoint’s normal price.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses the unauthenticated/signed-out viewpoint, the credit model (1 credit on success; errors, blocked, timed-out, invalid, and cache hits are free; not-found/empty charged only per published cost), and the exact-vs-null semantics of edge_owner_to_timeline_media.count. It omits what happens for private or nonexistent handles and any rate-limit behavior, and the count explanation is truncated mid-word ("shows a rounde").

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The endpoint and core purpose are front-loaded, and the field enumeration earns its space for an agent deciding relevance. However, it is a single dense run-on block, and the truncated sentence about the rounded count is a real structural defect that leaves a claim incomplete.

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?

There is no output schema, so the description compensates by naming the response envelope (data.user) and the fields returned, and it covers cost and caching behavior well. Remaining gaps are edge-case outcomes (private account, not-found) and the effect of trim on the payload, which an agent would need to call this confidently.

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 handle, trim, and cache_max_age are already documented, and the description adds little beyond the schema. The one meaningful addition is the cost statement about cache hits, which gives cache_max_age economic context, but trim's effect on the response shape is not elaborated anywhere in the description.

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?

The description names a specific verb and resource ("Get a public Instagram profile") and pins the scope precisely: "as a signed-out visitor sees it," returning the web_profile_info shape under data.user. It then enumerates the exact fields returned, which implicitly separates it from post-listing siblings like instagram_user_posts, but it never names an alternative tool explicitly.

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 rather than stated: the tool is for public profiles viewed unauthenticated, and the credit/cache sentences hint at cost tradeoffs. There is no explicit "use this instead of X when Y" routing, no guidance on when to prefer instagram_profile_post_count or instagram_user_posts for deeper post data, and no stated prerequisites or 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