Skip to main content
Glama
Sign In
Meta Ads MCP

Meta Ads MCP

by AbnerZx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

ig_get_account

Retrieve profile information for an Instagram Business account by providing its ID. Access account details needed for managing ads and insights.

Instructions

Get profile info for an IG Business account.

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": {
      "ig_account_id": "<ig_account_id>"
    },
    "name": "ig_get_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
ig_account_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavior. It only says 'Get', implying a read operation, but does not state permissions, rate limits, response shape, or what happens if the account is not a Business account.

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?

One sentence, no fluff, front-loaded with the verb. Efficient and appropriately sized for the simple tool.

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?

For a simple one-param tool without annotations or output schema, the description is too sparse. It doesn't explain the return value ('profile info' is not defined), nor does it provide context about account prerequisites or error conditions.

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 schema lists a single parameter ig_account_id with no description. The tool description does not explain what this ID is, how to obtain it, or its format. The parameter name is somewhat self-explanatory, but the description adds no additional semantic information.

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 states 'Get profile info for an IG Business account' with a specific verb and resource. It distinguishes from sibling tools like ig_get_account_insights and ig_list_accounts by focusing on profile info rather than insights or account lists. However, 'profile info' is somewhat vague regarding the exact fields returned.

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?

No guidance is provided on when to use this tool versus alternatives. It does not mention that for media or insights one should use other tools, nor any prerequisites or use cases.

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

Deploy Server

Other Tools