Skip to main content
Glama

instagram_read_post

Read-onlyIdempotent

Reads caption, author, and all exposed carousel slide metadata from a single Instagram post or Reel URL.

Instructions

Read caption, author and all exposed carousel slide metadata for one post or Reel.

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

Input Schema

NameRequiredDescriptionDefault
urlYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, and non-destructive, so the safety profile is covered by structured fields. The description adds real value with 'all exposed carousel slide metadata', hinting that some data may not be surfaced, but says nothing about auth, private posts, or failure behavior.

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?

A single front-loaded sentence with the verb and the returned fields in the first clause. No filler, though the trailing 'for one post or Reel' scoping could be tightened into the opening.

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

Completeness3/5

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

For a one-parameter read tool with annotations and an output schema, the essentials are present. Gaps remain around accepted URL formats and edge cases like private or deleted posts, which matter for correct invocation.

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 coverage is 0% for the single 'url' parameter, so the description carries the burden. It does clarify that the URL identifies one post or Reel, but does not specify whether a full URL, shortcode, or Reel link form is required, leaving the main ambiguity unresolved.

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?

The description opens with a specific verb ('Read') and enumerates the resource contents (caption, author, carousel slide metadata) scoped to a single post or Reel. That cleanly separates it from image/screenshot-oriented siblings, though it never names a sibling explicitly.

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?

The only usage signal is the implicit scope 'for one post or Reel'. There is no statement of when to prefer this over instagram_post_image, instagram_snapshot, or instagram_reel_artifact, and no prerequisites or exclusions are given.

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