Skip to main content
Glama
Sign In

Desearch

by io.github.Desearch-ai
OverviewDiscussionsAdmin

Instagram

instagram
Read-only

Read public Instagram data with Desearch. Set action and that action's arguments. search (query; optional count): profiles that match, one page with no cursor. media (id): one post by shortcode, numeric ID, or URL. profile (username): one profile. profile_posts (username; optional count, cursor): a user's posts. comments (shortcode; optional count, cursor): a post's comments. hashtag (tag; optional count, cursor): posts with a hashtag. media and profile return the item itself. List actions return { results, next_cursor, next }. For the next page, call again with the same action and target and cursor set to next_cursor, unchanged; next_cursor is null on the last page. A cursor lasts 24 hours.

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": {
      "action": "<action>"
    },
    "name": "instagram"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNomedia: the post shortcode, numeric media ID, or public URL.
tagNohashtag: the hashtag without #, example: 'ai'. A leading # is removed.
countNoMost items to return (1-100). API default: 10 for search, 20 for the other list actions. One page may hold fewer.
queryNosearch: keyword or phrase, example: 'desearch'.
actionYesWhat to read: 'search', 'media', 'profile', 'profile_posts', 'comments', or 'hashtag'.
cursorNonext_cursor from the previous page of the same action and target, sent back unchanged. Omit it for the first page.
usernameNoprofile, profile_posts: Instagram username, example: 'instagram'. A leading @ is removed.
shortcodeNocomments: the code in the post URL, such as 'DeuOR-CjKE9' in https://www.instagram.com/p/DeuOR-CjKE9/. Numeric media IDs return 404.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/openWorld/non-destructive, and the description adds context they cannot: which actions return a bare item versus { results, next_cursor, next }, that search is a single page with no cursor, and that a cursor expires after 24 hours. That pagination lifecycle and TTL is exactly the kind of operational detail an agent needs to avoid burned retries.

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 verb and action list, then pagination rules, with every sentence carrying information. It is dense — a long run-on enumeration of actions — but nothing is redundant enough to cut without losing routing value.

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 an 8-parameter, 6-action tool with no output schema, the description supplies return shapes, the paging contract, and cursor lifetime, which is what an agent would otherwise have to discover by trial. Nothing needed to invoke it correctly appears missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, and the description adds mapping value by binding each parameter to its action ('media (id)', 'comments (shortcode; optional count, cursor)'). It stops short of restating format rules already in the schema (shortcode vs numeric ID 404, leading #/@ stripping), so no higher than 4.

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?

States a specific verb and resource ('Read public Instagram data') and enumerates all six actions with their required arguments, so an agent can map a request to an action without opening the enum. The Instagram scope also separates it cleanly from siblings like facebook, tiktok, and x-search.

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

Usage Guidelines4/5

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

The action-by-action listing tells the agent exactly which action to pick for profiles, posts, comments, or hashtags, and which arguments each needs. It does not compare against non-Instagram siblings (e.g., web-search or search) or state any exclusions, which keeps it below a 5.

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

All Desearch 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