Instadata — Instagram Data API

Search a hashtag

search_hashtag

Read-onlyIdempotent

Public posts carrying a hashtag. Instagram only. Credits: 1 per item returned, and an empty result is free (25 a day per account, then 1 credit each). Input: query.

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": {
      "query": "<query>"
    },
    "name": "search_hashtag"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Items to return, up to 50; a larger value is lowered to 50, and free accounts get at most 5 (meta.limit_capped reports it). Credits are charged per item returned, and an empty result is free (25 a day per account, then 1 credit each).
`query`	Yes	Search keywords.
`cursor`	No	next_cursor from a previous call's meta.

Output Schema

Name	Required	Description
`data`	Yes	The endpoint's payload: one object, or an array for list calls.
`meta`	No	count, limit and next_cursor on list calls; credits_charged, credits_remaining and cache (hit or miss) on billed calls; limit_clamped when fewer items were requested upstream than the balance could cover; limit_capped when a free account's request was lowered to the free tier's 5-item ceiling.
`request_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 4, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world and non-destructive, so the safety profile is covered. The description adds genuinely useful behavior beyond them: per-item credit charging, free empty results, and a 25-per-day-per-account allowance before per-item charges. It omits result ordering and whether private accounts are excluded from "public posts".

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?

Everything is packed into one front-loaded block: scope, platform, cost, then input. The trailing "Input: query." is redundant with the schema's required field and is the only wasted clause.

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?

The tool has an output schema, so return values and meta.limit_capped need not be described. Given that, the description covers the two things an agent could not learn elsewhere at a glance: platform restriction and the credit/quota model that governs cost of a call.

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 the schema already documents query, limit and cursor in detail, including the 50 cap and the free-account cap of 5. The description's "Input: query." adds nothing beyond that, so the baseline 3 is appropriate.

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 the resource precisely (public posts carrying a hashtag) and adds a hard platform scope ("Instagram only"), which separates it from generic siblings like get_channel_posts or call_endpoint. It stops short of a clean verb-first statement and does not explicitly name the sibling that handles the non-Instagram or non-hashtag case.

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?

"Instagram only" gives a clear applicability constraint, and the credit/quota sentence implies this is a metered call to be used deliberately. However, there is no explicit when-to-use versus alternatives guidance against the nine siblings, so the agent must infer that hashtag lookups belong here rather than in get_channel_posts.

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

All Instadata — Instagram Data API tools Inspect

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

Need Help?