Skip to main content
Glama

Find a post by link

find_post
Read-only

Finds one of the creator's own posts or reels from its Instagram link, also older ones that list_posts doesn't show. Use its id as post_id.

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

Input Schema

NameRequiredDescriptionDefault
urlYesA post or reel link as Instagram shares it, e.g. https://www.instagram.com/reel/C9xY_ab-12/

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 readOnlyHint=true, so the description is free to add scope context, which it does: it only resolves the creator's own posts, it reaches older posts beyond list_posts' window, and it returns an id intended for use as post_id. It does not say what happens when the link is invalid or belongs to another account, which is a modest gap for a lookup tool.

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?

Two tight sentences with zero filler, front-loading the verb and scope before the downstream hint about post_id. Nothing repeats the title or the schema.

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?

For a single-parameter, read-only lookup with full schema coverage and annotations covering safety, the description supplies everything an agent needs: what it resolves, the ownership restriction, the fallback relation to list_posts, and what to do with the returned id. No output schema exists, yet the description still indicates the useful return value.

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 100% and the schema's example already shows the accepted link format, so the schema carries most of the load. The description still adds a real constraint the schema does not encode: the link must point to one of the creator's own posts or reels.

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 ('Finds one of the creator's own posts or reels from its Instagram link') and explicitly scopes it against the sibling list_posts by covering older posts that list_posts doesn't show. An agent can distinguish this from list_posts without opening either schema.

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 trigger: use this when you have an Instagram link and the post may be older than what list_posts surfaces. It also gives forward guidance ('Use its id as post_id'), which tells the agent what to do with the result. It stops short of explicit when-not-to-use cases, such as links to other creators' posts.

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