insta-pilot

ig_profile

Read-only

Fetch profile details—bio, follower and following counts, and total posts—for the configured Instagram account or the active one.

Instructions

Perfil de la cuenta: bio, seguidores, seguidos, nº de publicaciones.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ig_profile"
  }
}

Input Schema

Name	Required	Description	Default
`account`	No	Usuario de Instagram configurado (por defecto la cuenta activa)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 20, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds the returned data set, which substitutes for the missing output schema, but says nothing about freshness, rate limits, or behavior for private/suspended accounts.

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 compact sentence that front-loads the resource and lists the returned fields with zero filler. It is terse to the point of omitting any routing or behavioral guidance, but nothing is wasted.

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, listing the returned fields partially compensates for the absent output schema. However, an agent gets no guidance on account selection or when this profile read is preferable to the insights/analytics siblings.

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 optional 'account' parameter is fully documented in the schema, including its default behavior. The description adds no additional meaning about the parameter, so the 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?

The description names the resource (account profile) and enumerates the exact fields returned (bio, followers, following, post count), so an agent can distinguish it from analytics siblings like ig_account_insights or ig_media_insights. It lacks an explicit verb and never names an alternative, so it stops short of a 5.

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?

There is no indication of when to call this tool versus ig_accounts, ig_account_insights, or ig_analytics. The only implied usage is that it surfaces profile-level data, which the agent must infer.

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