Skip to main content
Glama
Sign In

Socify-mcp

by com.trysocify
OverviewDiscussionsAdmin

instagram_profile/media

Fetch recent public posts or Reels for a profile (paginated).. Platform=instagram resource=profile/media. 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": {
      "user": "<user>"
    },
    "name": "instagram_profile/media"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabNoposts (default) or reels.
userYesUsername, profile URL, or numeric user id.
cursorNoPagination cursor from a previous response.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / user / examples
      Previous value: -[
-  "natgeo"
-]New value: +[
+  "leomessi"
+]
  2. Changed2 schema fields changed
    • addedInput schema / properties / cursor
      Added value: +{
+  "description": "Pagination cursor from a previous response.",
+  "type": "string"
+}
    • removedInput schema / properties / posts
      Removed value: -{
-  "description": "Number of posts to fetch (1–12). Default 3.",
-  "examples": [
-    "3"
-  ],
-  "type": "string"
-}
  3. Changed3 schema fields changed
    • removedInput schema / properties / cursor
      Removed value: -{
-  "description": "Pagination cursor from a previous response.",
-  "type": "string"
-}
    • removedInput schema / properties / enrich
      Removed value: -{
-  "description": "Set to 1 to fill comments/video_url via per-item detail (much more bandwidth).",
-  "type": "string"
-}
    • addedInput schema / properties / posts
      Added value: +{
+  "description": "Number of posts to fetch (1–12). Default 3.",
+  "examples": [
+    "3"
+  ],
+  "type": "string"
+}
  4. Changed1 schema field changed
    • addedInput schema / properties / enrich
      Added value: +{
+  "description": "Set to 1 to fill comments/video_url via per-item detail (much more bandwidth).",
+  "type": "string"
+}
  5. Added

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose three real operational facts: results are public-only, paginated, and cost 1 credit per request, plus the Bearer auth requirement. It does not cover behavior for private/nonexistent profiles, rate limits, or what a page contains. This is meaningful but partially boilerplate context rather than rich behavioral disclosure.

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 core purpose is stated in the first clause and is front-loaded. It is short and free of filler, though the doubled period and the redundant platform/resource tag are minor blemishes on an otherwise tight definition.

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 three-parameter read tool with no output schema, the definition covers purpose, cost, auth, and pagination, which is close to sufficient. What is missing is return-shape expectation (since no output schema exists) and guidance on paging termination, so an agent cannot fully predict what it will get back.

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 all three parameters (tab, user, cursor) are already documented in the schema, including the posts/reels values. The description only reinforces the pagination concept via "(paginated)" and adds no detail on cursor lifecycle or resetting paging. Baseline 3 applies when the schema does the heavy lifting.

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 uses a specific verb and resource ("Fetch recent public posts or Reels for a profile") and scopes it to public content. It distinguishes itself implicitly from instagram_profile/info (profile metadata) and instagram_media/info (single media) through the plural "posts or Reels" framing, though it never names those siblings. The trailing "Platform=instagram resource=profile/media" is pure restatement and adds nothing.

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 only implied by the scope: fetch listings for a profile. There is no explicit guidance on when to choose this over instagram_profile/info or instagram_media/info, nor any stated prerequisites such as the profile needing to be public. An agent can infer the use case but must reason about alternatives itself.

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