Skip to main content
Glama
unofficial-instagram-mcp

unofficial-instagram-mcp

by fanyzp

hashtag_posts

Read-only

Lists posts from an Instagram hashtag page to support topic and niche research.

Instructions

Daftar post di halaman sebuah hashtag. Berguna untuk riset topik/niche.

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": {
      "tag": "<tag>"
    },
    "name": "hashtag_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagYes
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior2/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, which covers safety. Beyond that, the description adds no behavior: it does not say whether results are paginated, whether the tag must be public, what the limit bounds are, or how many posts are returned by default. For a list tool that can pull large result sets, that is a real gap.

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, with the core operation stated first and the use case second. Nothing is redundant, although the brevity comes at the cost of under-specification rather than through efficient density.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description would need to describe the return shape or ordering of posts, and it does not. Both parameters are undocumented and the read-only, open-world nature depends entirely on the annotations. The definition is too thin for an agent to call it confidently.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must explain both parameters. It never states whether 'tag' includes or omits the leading '#', and it never mentions 'limit' at all, leaving the agent to guess the default page size and the maximum. Only the word 'hashtag' indirectly hints at the tag format.

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 gives a specific verb and resource: it lists posts on a hashtag page. An agent can tell it apart from a generic feed tool because the hashtag scope is explicit. It does not contrast itself with siblings like explore_posts or user_posts, which keeps it from a 5.

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?

The phrase about topic/niche research implies a use case but gives no conditions for when to choose this tool over alternatives such as search or explore_posts, and no exclusions. Usage is inferable rather than stated.

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