Skip to main content
Glama
Meta Ads MCP

Meta Ads MCP

by kremnyi

auth_status

Read-onlyIdempotent

Check the Meta access token's permissions and expiry, and report the configured ad account to confirm API access is ready.

Instructions

Check the Meta access token, its permissions and expiry, and the configured ad account.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description usefully discloses what data is inspected (permissions, expiry, configured account), but says nothing about what happens with an invalid or expired token — error versus a status payload — which matters most for a diagnostic tool.

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?

A single sentence with no filler, front-loading the verb and enumerating the three things checked. 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?

For a zero-parameter read-only diagnostic with full annotation coverage, the description covers what is inspected, which is the key return-value hint in the absence of an output schema. Only the failure behavior of an invalid token is left unaddressed.

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 there is no schema semantics to compensate for; the baseline of 4 applies. Nothing in the description contradicts the empty object schema.

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 the Meta access token, its permissions and expiry, and the configured ad account" gives a specific verb plus an enumerated set of resources, so an agent knows exactly what it inspects. It does not explicitly contrast with the ambiguous sibling "set_status" or "get", but the scope is narrow enough to be self-evident.

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?

The description contains no when-to-use or when-not-to-use guidance and names no alternatives. An agent must infer on its own that this is a pre-flight diagnostic to run before other Meta operations, or after a suspected permission failure.

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