Skip to main content
Glama

resolve_reel_by_link

Read-onlyIdempotent

Resolve a pasted Instagram permalink (a reel/post/carousel URL, e.g. https://www.instagram.com/reel/XXXXXXXXXXX/) to its Instagram media id — what an automation's post_target="specific" targets internally, not this tool's own id fields.

Use this when the user gives you a link directly instead of picking from get_reel_analytics/list_scheduled_posts — e.g. an older post outside the default analytics window, or one posted natively and never scheduled through reeldrop. Only resolves the account's ~100 most recent posts (Instagram doesn't offer a direct permalink lookup); an older link returns "not found" rather than a partial guess.

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

Input Schema

NameRequiredDescriptionDefault
urlYes
workspace_idYes

Output Schema

NameRequiredDescriptionDefault
permalinkYes
media_typeNo
ig_media_idYes
thumbnail_urlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the read-only, idempotent, non-destructive annotations, the description discloses the key hidden limitation: only about the 100 most recent posts are resolved because Instagram has no direct permalink lookup. It also explains that older links return "not found" rather than a partial guess, which is important operational context.

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?

The definition is front-loaded with the core purpose, followed by usage guidance and then the key limitation. Every sentence adds useful context, and the parenthetical clarification about post_target prevents a likely misunderstanding without becoming bloated.

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?

Given the tool's complexity, the existing output schema, and the annotations, the description is complete enough to call correctly. It covers purpose, usage alternatives, output meaning, and the major resolution limitation; the only minor omission is workspace_id semantics.

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 0%, so the description must carry parameter meaning. It explains the url parameter well as a pasted reel/post/carousel permalink with an example, but it does not explain the required workspace_id parameter, leaving one of two parameters without semantic guidance.

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?

The description states a specific verb and resource: resolving an Instagram permalink to its media id. It also distinguishes the output from the tool's own id fields and names the automation post_target use case, so an agent can tell exactly what it does and why it exists.

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

Usage Guidelines5/5

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

It explicitly says when to use this tool: when the user provides a link directly instead of choosing from get_reel_analytics or list_scheduled_posts. It gives concrete scenarios such as older posts or natively posted content, and states the failure condition for unsupported older links.

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