Skip to main content
Glama

get_instagram_identities

List Instagram accounts linked to your ad account and retrieve their canonical user IDs for identity resolution in ad targeting.

Instructions

List Instagram accounts available for ads on a specific ad account.

Returns instagram_user_id (the canonical identifier) for each account. This is the first step in the Instagram identity resolution ladder.

Args: account_id: Ad account ID (e.g., 'act_123456789').

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
account_idYes
Behavior3/5

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

No annotations are provided, so the description bears full responsibility. It indicates a read operation by saying 'list' and mentions return value, but lacks details on authentication needs, error handling, or prerequisites like linked Instagram accounts.

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 extremely concise with only two sentences plus an argument line, no fluff, and front-loaded with the main purpose. Every sentence adds value.

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

Completeness4/5

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

For a simple one-parameter tool with no output schema and no annotations, the description adequately explains purpose and parameter usage. It could be more complete by describing the response format (e.g., list of objects or strings) and error conditions, but overall it is fairly complete given the tool's simplicity.

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

Parameters4/5

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

The input schema has one parameter with no description, but the description adds meaning by providing the format and example ('act_123456789'). This compensates for the 0% schema description coverage.

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 specifies the tool lists Instagram accounts available for ads on a specific ad account, uses verb 'list', and mentions returning the canonical identifier. It distinguishes from siblings by stating it's the first step in the Instagram identity resolution ladder.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides context by stating it's the first step in the identity resolution ladder, implying its use before other steps. However, it does not explicitly mention when not to use it or alternative tools, but the context is clear enough.

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/brandu-mos/konquest-meta-ads-mcp'

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