Skip to main content
Glama
Instagram Campaign MCP

Instagram Campaign MCP

by enimarix

get_account_pages

Read-only

List Facebook Pages for the current token and get their linked Instagram Business Account IDs to use as INSTAGRAM_BUSINESS_ACCOUNT_ID in campaign API calls.

Instructions

List Facebook Pages for this token and their linked Instagram account IDs (use the id as INSTAGRAM_BUSINESS_ACCOUNT_ID).

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_account_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.9/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 and external-scope profile is covered. The description adds real context beyond that by scoping results to 'this token' (an auth dependency) and naming what is returned, but it says nothing about rate limits, pagination, or the empty-pages case.

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?

Two short clauses with zero filler, and the primary purpose is front-loaded ahead of the parenthetical usage note. Nothing could be removed without losing information.

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?

With no parameters, a declared output schema, and safety annotations in place, the description covers the essentials: token scoping, return contents, and downstream use of the IDs. Only minor operational details (pagination, empty result behavior) are absent, and the output schema carries the return shape.

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 tool takes zero parameters, so the baseline of 4 applies and there is no parameter meaning left to compensate for. The mention of INSTAGRAM_BUSINESS_ACCOUNT_ID describes downstream consumption of the output rather than an input to this call.

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 gives a specific verb and resource ('List Facebook Pages for this token') plus the secondary payload ('their linked Instagram account IDs'), so an agent knows exactly what the call returns. It does not explicitly name a sibling it differs from, which keeps it just below a 5.

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 parenthetical '(use the id as INSTAGRAM_BUSINESS_ACCOUNT_ID)' establishes the concrete downstream use: this is the discovery/bootstrap call whose output feeds the Instagram-scoped tools. Guidance is clear but there are no explicit exclusions or named alternatives, so it stops short of a 5.

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