Skip to main content
Glama
Instagram Campaign MCP

Instagram Campaign MCP

by enimarix

validate_access_token

Read-only

Checks that the configured Instagram access token works before publishing, scheduling, or moderating campaigns to prevent authentication errors.

Instructions

Check that the configured access token works.

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": "validate_access_token"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.4/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 safety and network reach are covered structurally, and "configured" adds the useful fact that no credential argument is supplied. However, the description never states what an invalid or expired token produces (error vs. false), nor whether the call consumes API quota — meaningful for a network probe.

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?

A single front-loaded sentence with no filler or redundancy. It is arguably too sparse rather than padded, but every word earns its place.

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?

An output schema exists to describe the return value and the annotations cover the read-only, network-facing profile, so the description need not explain results. The main remaining gap — failure semantics and whether quota is consumed — is minor for a zero-parameter probe.

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 is 4; the word "configured" reinforces that the token comes from stored configuration rather than input. Nothing further is needed on the parameter front.

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?

"Check that the configured access token works" names a specific verb (check) and resource (the configured access token), and "configured" signals that the credential is already stored rather than passed in. It does not reference any sibling, but no sibling in the catalog performs credential validation, so differentiation is not a real gap.

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?

There is no when-to-use guidance at all: nothing says to call it before publishing, after a credential change, or on auth failures, and no alternative or prerequisite is named. The agent must infer the trigger condition entirely.

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