Socify-mcp

instagram_profile/info

Fetch a public Instagram profile by username, profile URL, or user id.. Platform=instagram resource=profile/info. 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/info"
  }
}

Input Schema

Name	Required	Description	Default
`user`	Yes	Username, profile URL, or numeric user id.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 7, 2026
- changedInput schema / properties / user / examples
```
Previous value: -[
-  "natgeo"
-]New value: +[
+  "leomessi"
+]
```
AddedNov 3, 2026

TDQS

B3.2/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 behavioral burden. It usefully discloses that this is a public-profile fetch, that it costs 1 credit per request, and that it requires bearer authorization, but it does not describe response behavior, rate limits, or error conditions.

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 purpose is front-loaded and the description is short. There is minor redundancy in restating platform/resource metadata that overlaps with the tool name, plus a double period, but it remains easy to scan.

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 simple one-parameter retrieval tool, the description covers the essential input, auth, and cost context. However, with no output schema, it does not describe what profile information is returned, leaving a gap for an agent trying to predict the response.

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 100% and the single parameter already documents that it accepts a username, profile URL, or numeric user id. The description repeats that meaning in prose but does not add syntax, formatting, or validation details beyond the schema.

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: fetching a public Instagram profile. It clearly states the accepted identifiers (username, profile URL, or user id), though it does not explicitly differentiate itself from siblings such as instagram_profile/media or instagram_media/info.

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?

It implies usage by saying it fetches a public Instagram profile, but gives no explicit when-to-use guidance and no alternatives or exclusions versus sibling tools. The identifier options are parameter details rather than usage guidance.

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

All Socify-mcp tools Inspect

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

Need Help?