Skip to main content
Glama
Sign In
meta-mcp

meta-mcp

by mikusnuz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ig_respond_collaboration_invite

Accept or decline an Instagram collaboration invite by media_id, using the invites returned from ig_get_collaboration_invites to finalize a collaboration request.

Instructions

Accept or decline a collaboration invite. Added in December 2025.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ig_respond_collaboration_invite"
  }
}

Input Schema

NameRequiredDescriptionDefault
acceptNotrue to accept, false to decline
actionNoLegacy alternative to accept
media_idNoInvited media_id returned by ig_get_collaboration_invites
invite_idNoLegacy alias for media_id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv2.2.2
    • addedInput schema / properties / accept
      Added value: +{
+  "description": "true to accept, false to decline",
+  "type": "boolean"
+}
    • changedInput schema / properties / action / description
      Previous value: -"Accept or decline the invite"New value: +"Legacy alternative to accept"
    • changedInput schema / properties / invite_id / description
      Previous value: -"Collaboration invite ID"New value: +"Legacy alias for media_id"
    • addedInput schema / properties / media_id
      Added value: +{
+  "description": "Invited media_id returned by ig_get_collaboration_invites",
+  "type": "string"
+}
    • removedInput schema / required
      Removed value: -[
-  "invite_id",
-  "action"
-]
  2. First observedv2.0.1

TDQS

C2.8/5.0
Behavior2/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, yet it discloses nothing about mutability, reversibility, whether a declined invite can be revisited, or what the response looks like. The only extra sentence, 'Added in December 2025,' is versioning metadata with no behavioral value.

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

Conciseness3/5

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

The first sentence is tight and front-loaded. The second sentence is pure filler that occupies space without informing an agent's decision.

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?

A mutation tool with zero annotations, no output schema, and four optional parameters where none are required — the description should clarify that an accept/decline choice plus a media_id is required in practice. It leaves that gap entirely to the consumer.

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%, and the schema itself explains accept vs action, media_id vs invite_id, and the enum. Baseline 3 applies since the schema does the heavy lifting and the description adds nothing beyond it.

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 pair (accept or decline) with a specific resource (collaboration invite), which is unambiguous. It does not explicitly differentiate from the obviously related sibling ig_get_collaboration_invites, though the pairing is inferable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No indication of when to use this versus alternatives, no prerequisite stated (e.g. that the media_id must come from ig_get_collaboration_invites, which only appears inside the schema text). An agent gets no guidance on sequencing or on what to do if no invite exists.

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