Skip to main content
Glama
Sign In
meta-mcp

meta-mcp

by mikusnuz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ig_get_mentioned_comments

Retrieve comments where your Instagram account is @mentioned and return the associated media and comment details for review or response.

Instructions

Get comments where the account was @mentioned. Returns the media and comment details.

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": {
      "comment_id": "<comment_id>"
    },
    "name": "ig_get_mentioned_comments"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoMentioned comment fields (default: id,text,timestamp,media{id,media_url,media_type})
comment_idYesComment ID from a mention notification

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.2.2
    • addedInput schema / properties / comment_id / pattern
      Added value: +"^\\d+$"
    • changedInput schema / properties / fields / description
      Previous value: -"Fields to return (default: id,text,timestamp,username,media)"New value: +"Mentioned comment fields (default: id,text,timestamp,media{id,media_url,media_type})"
  2. First observedv2.0.1

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose what comes back ('media and comment details'), which is useful without an output schema, but says nothing about pagination, rate limits, or whether the call is scoped to a single comment_id versus a list of mentions.

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 no filler, front-loaded with the operation and scope. Not padded, though also not structured with any usage detail.

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 two-parameter read tool with full schema coverage and no output schema, the description covers purpose and return content adequately. The main gap is whether this returns one comment (given required comment_id) or a collection of mentions.

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%: both fields and comment_id are documented in the schema (including the default field list and the mention-notification origin of the ID). The description adds nothing parameter-specific, so baseline 3 applies.

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?

States a specific verb ('Get') and resource ('comments where the account was @mentioned'), which is meaningfully narrower than ig_get_comments and ig_get_comment. It does not explicitly name those siblings, but the '@mentioned' scoping makes the resource distinguishable.

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 '@mentioned' qualifier implies the use case (handling mention notifications), but there is no explicit when/when-not guidance and no mention of the obvious alternative ig_get_comments for comments on your own media. Routing must be inferred.

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

Deploy Server

Other Tools