Skip to main content
Glama
Instagram Campaign MCP

Instagram Campaign MCP

by enimarix

search_hashtag

Read-only

Retrieve top or recent public Instagram posts for a specified hashtag to research campaign content and hashtag performance. Choose the post edge and result limit.

Instructions

Top or recent public posts for a hashtag. Meta caps lookups at 30 unique hashtags per 7 days, so pick them deliberately.

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": "search_hashtag"
  }
}

Input Schema

NameRequiredDescriptionDefault
edgeNotop_media
limitNo
hashtagYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds a genuinely non-obvious behavioral constraint: a 30-unique-hashtag/7-day lookup cap that affects how an agent should batch or sequence calls. It stops short of noting pagination behavior, but the output schema covers return shape.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with what the tool returns and followed by the operational constraint. Nothing is redundant or padded.

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 simple three-parameter read tool with an output schema, the description covers purpose and the key rate-limit hazard. The remaining gap is input formatting (hashtag prefix, limit semantics), which is a modest but real omission given 0% schema coverage.

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 carry parameter meaning. It partially maps the edge parameter by saying "top or recent," but never states whether the hashtag value should include or omit the '#' prefix, what limit controls, or how the two modes differ in results.

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?

"Top or recent public posts for a hashtag" states a concrete resource and the two retrieval modes, so an agent knows exactly what comes back. It does not explicitly differentiate itself from siblings, though no sibling in the listed catalog performs hashtag lookups, so the ambiguity cost is low.

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 quota sentence ("Meta caps lookups at 30 unique hashtags per 7 days, so pick them deliberately") gives real usage pressure and implies deliberate, sparing use. There is no explicit when-not guidance or named alternative for other discovery needs, so usage is only implied.

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