Skip to main content
Glama
Sign In

Socify-mcp

by com.trysocify
OverviewDiscussionsAdmin

instagram_search

Search public Instagram posts and Reels by keyword (paginated).. Platform=instagram resource=search. Costs 1 credit(s) per request. Requires Authorization: Bearer <api_key>.

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": {
      "query": "<query>"
    },
    "name": "instagram_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesKeyword or topic to search for.
cursorNoPagination cursor from a previous response.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / cursor
      Added value: +{
+  "description": "Pagination cursor from a previous response.",
+  "type": "string"
+}
    • changedInput schema / properties / query / description
      Previous value: -"Search text."New value: +"Keyword or topic to search for."
    • changedInput schema / properties / query / examples
      Previous value: -[
-  "natgeo"
-]New value: +[
+  "mountain bike"
+]
  2. Added

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does disclose the important operational traits: pagination, a per-request cost of 1 credit, and an Authorization Bearer requirement. It does not state result shape or rate limits, but the cost/auth/pagination disclosure is meaningful context an agent cannot get from structured fields.

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?

The core capability is front-loaded in the first clause, followed by short operational facts. The 'Platform=instagram resource=search' segment is low-value boilerplate and the stray double period is sloppy, but the whole description is only three short sentences.

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

Completeness4/5

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

For a two-parameter keyword search with no output schema, the description covers purpose, pagination, cost, and auth — enough to call it correctly. The main remaining gap is any indication of what a result contains, which matters slightly more here because no output schema exists.

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%, so both parameters are already documented, and the description only restates them at a high level ('by keyword', 'paginated'). It adds no syntax, cursor-lifetime, or matching-behavior detail beyond the schema, so baseline 3 applies.

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 and resource ('Search public Instagram posts and Reels by keyword'), which clearly separates it from profile/media/info siblings. It stops short of naming which sibling to use for non-keyword lookups, so the differentiation is inferred rather than stated.

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

Usage Guidelines3/5

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

Usage is implied by the phrase 'public Instagram posts and Reels by keyword', which tells the agent this is keyword discovery, not entity lookup. There is no explicit when-to-use versus alternatives (e.g. instagram_profile/media or hashtag search) and no statement of when not to use it.

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

All Socify-mcp toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources