Skip to main content
Glama
Sign In

Instagram Data

by io.github.FastSocialCo
OverviewDiscussionsAdmin

Instagram user id to username

instagram_username
Read-only

Instagram user id to username. The current handle for a numeric user id, which still works after the account renames itself.

Cost: 2 credits.

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": {
      "user_id": "<user_id>"
    },
    "name": "instagram_username"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_idYesNumeric Instagram user id. id= also works.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / user_id / description
      Previous value: -"Numeric Instagram user id. Pass this or username."New value: +"Numeric Instagram user id. id= also works."
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds genuine behavioral context beyond that: a concrete cost (2 credits) and a freshness guarantee that the returned handle survives account renames.

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 plus a cost line, with the useful freshness detail front-loaded. Slightly wasteful in that the opening sentence nearly restates the title, but overall tight.

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 single-param, read-only lookup whose return value (a username) is self-evident, the description is sufficient: purpose, what it returns, freshness behavior, and cost. No output schema is needed for such an obvious return.

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 coverage is 100% and the single user_id param is fully documented with an example. The description only restates 'numeric user id,' adding nothing beyond the schema, so 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?

The description states a specific verb+resource: converting a numeric Instagram user id to its current handle. It is crisply defined and implicitly distinct from the reverse sibling instagram_user_id, though it never names that sibling to make the direction explicit.

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 only implied: 'the current handle for a numeric user id, which still works after the account renames itself' hints you should prefer this when a cached handle may be stale. There is no explicit when-to-use/when-not framing and no routing toward or away from instagram_user_id.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Instagram Data toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources