Skip to main content
Glama

add_grid_collab

Add a Collab post to the grid by its Instagram link. A post co-authored with another account is counted on the profile but Instagram's API never returns it for the account, so it is missing from the grid until added by link here.

url is the post's link (instagram.com//p// or /reel/…). Pass username (the other account's handle, no @) only when the link does not contain it — the short share form instagram.com/p//. Up to 100 collabs. The post's date is read from the link itself.

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": {
      "workspace_id": "<workspace_id>",
      "url": "<url>"
    },
    "name": "add_grid_collab"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
usernameNo
workspace_idYes

Output Schema

NameRequiredDescriptionDefault
idYes
modeYes
sourceYes
captionYes
permalinkNo
published_atNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent, closed-world write, so the safety profile is covered. The description adds genuine domain context beyond that: the reason the post is absent, the 100-collab cap, and that the post date is derived from the link rather than supplied. It does not say what happens if the same link is added twice, which matters given idempotentHint=false.

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?

Four short blocks: purpose, rationale, parameter rules, and the collab limit plus date behavior. The rationale is front-loaded ahead of the parameter guidance, and every sentence contributes either a triggering condition or a formatting rule.

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

Completeness5/5

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

With an output schema present, return values need no explanation, and the description covers what an agent actually needs to invoke correctly: input formats, the conditional username rule, the 100-collab ceiling, and how the date is determined. The only plausible omission, workspace_id semantics and duplicate-add behavior, is minor against 3 total parameters.

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 0%, so the description carries the full parameter burden — and it delivers for two of three. It gives accepted URL shapes (instagram.com/<handle>/p/<code>/ and /reel/…), and specifies the exact conditional for `username` (only when the link lacks the handle, as in the short share form instagram.com/p/<code>/) plus the no-@ format. `workspace_id` is never mentioned, leaving one required parameter unexplained.

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 and resource ('Add a Collab post to the grid by its Instagram link') and immediately explains the underlying data condition that makes the operation necessary — co-authored posts that the API never returns. This is far more distinguishing than a bare name restatement and separates it from placeholder/removal siblings like remove_grid_collab.

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?

Gives a clear triggering condition: use this when a co-authored post is missing from the grid because the API doesn't return it. It also states the operational ceiling ('Up to 100 collabs'). It does not explicitly say when to prefer create_grid_placeholder or convert_grid_placeholder instead, so it stops short of full alternative routing.

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.

Resources