Skip to main content
Glama

instagram: Posts under a hashtag

instagram_hashtagPosts
Read-only

Posts under a hashtag. Posts carrying a hashtag: the top posts Instagram shows a logged-out visitor on the tag page, one page with no cursor. tab=recent returns the same top posts, because Instagram serves its chronological list only to signed-in viewers. Instagram shows some tags only to signed-in viewers; those answer that the tag is not publicly available, and are not charged. Set extra_fetch=true to fill each post's publish date, like and comment counts and caption from its own page: 1 credit per item fetched, up to the page size. Costs 1 credit.

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": {
      "hashtag": "<hashtag>"
    },
    "name": "instagram_hashtagPosts"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabNoKept for compatibility: both return the top poststop
cursorNoIgnored: the tag page has no further page for a logged-out visitor
hashtagYesHashtag (#nasa or nasa), or an /explore/tags/ URL
extra_fetchNoWhen true, fetches each item's own page to fill fields the list page leaves null. Costs 1 extra credit per page fetched, up to the page size.
cache_max_ageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / cursor / description
      Previous value: -"`pagination.cursor` from a previous response. `recent` only"New value: +"Ignored: the tag page has no further page for a logged-out visitor"
    • changedInput schema / properties / tab / description
      Previous value: -"Instagram's ranking, or chronological"New value: +"Kept for compatibility: both return the top posts"
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Goes well beyond the readOnly/openWorld annotations: discloses single-page/no-cursor behavior, that `tab=recent` is a no-op, that signed-in-only tags return 'not publicly available' and are not charged, and that extra_fetch costs 1 credit per item fetched up to page size. This is unusually rich cost and failure-mode disclosure; only pagination-free return shape is left implicit.

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-loads the definition of what is returned, then pricing quirks, then the extra_fetch tradeoff. Slightly repetitive opening ('Posts under a hashtag. Posts carrying a hashtag:') and the credit cost is stated twice, but otherwise dense and purposeful.

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-page, credit-metered scraper with no output schema, the description covers paging limits, cost model, and the failure case for non-public tags. It does not describe the shape of returned post objects (which fields are null without extra_fetch), leaving that to be inferred.

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 already 80%, yet the description adds real meaning: it explains why `tab` and `cursor` are inert (compatibility/no further page) and quantifies the per-item credit cost of `extra_fetch`. Only `cache_max_age` remains unexplained in both schema and description.

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+resource ('Posts under a hashtag') and immediately defines the exact scope: the top posts a logged-out visitor sees on a tag page, one page only. That scope definition distinguishes it from broader search/profile-post siblings without naming them.

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?

Clearly explains the tradeoff between the default call and `extra_fetch=true` (extra fields vs 1 credit per item), and warns that `tab=recent` is useless. It does not name any sibling tool (e.g. instagram_userTaggedPosts or instagram_search) as an alternative for related queries, so routing guidance is contextual rather than explicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.