Skip to main content
Glama
Sign In
meta-ads-mcp

meta-ads-mcp

by fujioka0729
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

meta_ads_save_token

Saves a Meta Ads API access token and automatically converts short-lived tokens to long-lived tokens valid for 60 days.

Instructions

Graph API Explorerで取得したアクセストークンを保存します。short-livedトークンは自動的にlong-lived（60日有効）に交換されます。

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": {
      "access_token": "<access_token>"
    },
    "name": "meta_ads_save_token"
  }
}

Input Schema

NameRequiredDescriptionDefault
access_tokenYesGraph API Explorerで取得したアクセストークン

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries full burden. It discloses the automatic token exchange to long-lived (60 days), but omits other effects like overwriting existing tokens or required permissions.

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 two sentences with no extraneous words. It front-loads the primary action and efficiently conveys the key behavior.

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

Completeness3/5

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

For a simple save tool with one parameter and no output schema, the description adequately covers purpose and key behavior. However, it lacks information on return values or error conditions.

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

Parameters3/5

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

Schema coverage is 100% with a clear parameter description. The tool description adds the automatic exchange behavior, but this is about the tool's action rather than parameter semantics, so minimal added value above baseline.

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 states it saves an access token from Graph API Explorer. It distinguishes itself from siblings like meta_ads_authenticate by specifying the source and automatic long-lived exchange.

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

Usage Guidelines3/5

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

The description implies usage after obtaining a token from Graph API Explorer but does not explicitly contrast with alternatives like meta_ads_authenticate or provide when-not-to-use guidance.

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