Skip to main content
Glama
Instagram Campaign MCP

Instagram Campaign MCP

by enimarix

get_profile_info

Read-only

Retrieve an Instagram account's username, bio, follower count, and post count to verify profile details and support campaign targeting decisions.

Instructions

Profile of the configured account: username, bio, followers, post count.

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

Input Schema

NameRequiredDescriptionDefault
account_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

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 openWorldHint=true, so the safety profile is covered by structured data. The description adds only the field list, which largely duplicates what the existing output schema conveys, and says nothing about caching, freshness, or error behavior on invalid credentials.

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 short sentence with no filler, and the key qualifier ("configured account") is front-loaded. It is efficient, though the fragmentary phrasing leaves little room for the guidance the tool needs.

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?

The tool is simple, annotations cover read safety, and an output schema documents the return payload, so the description does not need to explain return values. However, it is incomplete on the one open question an agent faces: how account_id interacts with the "configured account" default.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter account_id has 0% schema description coverage and is optional with a null default, yet the description never explains what it does or what omitting it means (presumably the configured account, but that is inferred from the phrase "configured account" rather than stated). With low coverage the description should have compensated and does not.

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?

Names a specific resource (the configured account's profile) and enumerates the returned fields: username, bio, followers, post count. The phrase "configured account" implicitly distinguishes it from get_competitor_profile, but it never names that sibling explicitly, so the differentiation is left to inference.

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: an agent can infer this is for reading the authenticated account's own profile rather than a competitor's, but there is no explicit statement of when to call this versus get_competitor_profile or get_account_insights, and no preconditions mentioned.

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