Skip to main content
Glama

exchange_token

Exchange a short-lived access token for a long-lived token to extend its validity.

Instructions

Exchange a short-lived access token for a long-lived token. Requires META_APP_ID and META_APP_SECRET to be configured.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
short_lived_tokenYesShort-lived access token to exchange

Implementation Reference

  • src/tools/auth.ts:5-21 (registration)
    Registration of the 'exchange_token' tool on the MCP server via server.tool(), defining name, description, Zod schema, and handler.
    export function registerAuthTools(server: McpServer, client: AdsClient): void {
      // ─── exchange_token ───────────────────────────────────────────
      server.tool(
        "exchange_token",
        "Exchange a short-lived access token for a long-lived token. Requires META_APP_ID and META_APP_SECRET to be configured.",
        {
          short_lived_token: z.string().describe("Short-lived access token to exchange"),
        },
        async ({ short_lived_token }) => {
          try {
            const { data } = await client.exchangeToken(short_lived_token);
            return { content: [{ type: "text" as const, text: JSON.stringify(data, null, 2) }] };
          } catch (error) {
            return { content: [{ type: "text" as const, text: `Failed: ${error instanceof Error ? error.message : String(error)}` }], isError: true };
          }
        }
      );
  • Zod input schema for exchange_token: requires a single string parameter 'short_lived_token'.
    {
      short_lived_token: z.string().describe("Short-lived access token to exchange"),
    },
  • Handler function that calls client.exchangeToken(short_lived_token) and returns the JSON result.
    async ({ short_lived_token }) => {
      try {
        const { data } = await client.exchangeToken(short_lived_token);
        return { content: [{ type: "text" as const, text: JSON.stringify(data, null, 2) }] };
      } catch (error) {
        return { content: [{ type: "text" as const, text: `Failed: ${error instanceof Error ? error.message : String(error)}` }], isError: true };
      }
    }
  • Core implementation of the token exchange API call: builds URL with fb_exchange_token grant type, calls Facebook's /oauth/access_token endpoint, validates response, and returns data.
    /** Exchange short-lived token for long-lived token */
    async exchangeToken(shortToken: string): Promise<ClientResponse> {
      if (!this.config.appId || !this.config.appSecret) {
        throw new Error(
          "META_APP_ID and META_APP_SECRET are required for token exchange."
        );
      }
      const qs = new URLSearchParams({
        grant_type: "fb_exchange_token",
        client_id: this.config.appId,
        client_secret: this.config.appSecret,
        fb_exchange_token: shortToken,
      });
      const url = `${this.baseUrl}/oauth/access_token?${qs.toString()}`;
      const res = await fetch(url, { signal: AbortSignal.timeout(30_000) });
    
      if (!res.ok) {
        const text = await res.text().catch(() => "");
        throw new Error(`Token exchange failed (${res.status}): ${text}`);
      }
    
      const data = await res.json();
      if (data.error) {
        throw new Error(this.formatError(data));
      }
      return { data };
    }
  • src/index.ts:93-94 (registration)
    Registration call of registerAuthTools(server, client) in the main entry point to wire the tool into the MCP server.
    registerAuthTools(server, client);

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations exist, so the description carries the full burden of disclosing behavior. It mentions a configuration requirement but does not state what the exchange does beyond the token conversion, whether it is a read-only operation, what the response contains, or any side effects. This is a significant gap for an authentication-related 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?

The description is two sentences, each serving a purpose: one states the core function, the other notes a necessary configuration. There is no redundancy or filler, making it appropriately concise and front-loaded.

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 single-parameter tool, the description covers the main action and a key requirement. However, it omits information about the returned token, potential errors, and the broader context of when to use this exchange. Since there are no annotations or output schema, the description could be more complete, earning a mid-range score.

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?

The schema describes the parameter 'short_lived_token' fully (100% coverage), and the description's phrase 'short-lived access token' aligns with the schema. The description does not add extra semantic details about the parameter beyond what the schema provides, so the baseline score of 3 applies.

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 the action ('Exchange') and the specific resources ('short-lived access token' to 'long-lived token'), making the tool's purpose unmistakable. It is specific enough to distinguish from related token tools like refresh_token and debug_token, even though alternatives aren't named.

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 the usage context (when you have a short-lived token and need a long-lived one) and provides a key prerequisite (META_APP_ID and META_APP_SECRET configured). However, it does not explicitly mention when to use this tool versus refresh_token or debug_token, nor any exclusions.

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