Skip to main content
Glama

Get Instagram Business / Creator account

ig_business_account_get

Retrieve Instagram Business Account details by providing the account ID and the linked Facebook Page ID for authentication.

Instructions

GET /{ig_user_id}. Note: ig_user_id is NOT the @username — it's the IG Business Account id obtained via /{page_id}?fields=instagram_business_account. Requires the Page Access Token of the linked Facebook Page (resolved automatically via via_page_id).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ig_user_idYes
via_page_idYes
fieldsNo
Behavior3/5

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

No annotations are provided, so the description must fully disclose behavior. It explains the authentication mechanism and the nature of the id parameter, but does not describe the return data or any side effects, which is a gap.

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 description is concise with two sentences, front-loads the endpoint, and adds critical notes without fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description is incomplete for a tool with no output schema and no annotations. It fails to mention what the response contains, error conditions, or any pagination details, leaving the agent underinformed.

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 schema has 0% description coverage, so the description must compensate. It explains ig_user_id and via_page_id, but the 'fields' parameter is left undocumented, leaving part of the meaning unclear.

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 clearly states it retrieves an Instagram Business/Creator account via GET endpoint, and the note about ig_user_id vs username adds specificity. However, it does not explicitly distinguish from sibling tools like ig_media_get beyond context.

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 explains the prerequisite of obtaining ig_user_id from a linked Facebook Page and the need for a Page Access Token, but it lacks guidance on when not to use this tool or comparison to alternatives.

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/nourpups/meta-mcp'

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