Skip to main content
Glama
exileum

meta-mcp

ig_business_discovery

Read-only

Fetch public profile data from any Instagram Business or Creator account using their username. Ideal for gathering account insights and analytics.

Instructions

Look up another Instagram Business/Creator account's public info by username.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fieldsNoFields to retrieve (default: id,username,name,biography,followers_count,follows_count,media_count)id,username,name,biography,followers_count,follows_count,media_count
usernameYesInstagram username to look up (1-30 chars, letters/numbers/periods/underscores only; without @, leading '@' characters and surrounding whitespace are auto-stripped)
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds 'public info' which aligns with read-only behavior but does not elaborate on rate limits, authentication, or other traits. No contradiction.

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 description is a single clear sentence. It is concise but could be slightly more structured with a brief note on usage.

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?

No output schema exists. The description hints at 'public info' but does not specify exact return fields. The default fields in the input schema partially compensate, making it adequate but not complete.

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?

The input schema provides full descriptions for both parameters (username format/auto-stripping, fields with defaults). The description adds no additional parameter meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool looks up public info of another Instagram Business/Creator account by username, distinguishing it from ig_get_profile which retrieves info for the connected account.

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?

The description implies usage for looking up other accounts but does not explicitly state when to use this tool versus alternatives like ig_get_profile. No exclusions or context provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/exileum/meta-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server