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);
Behavior3/5

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

With no annotations, the description adds some behavioral context by mentioning required app credentials, but it does not disclose behavioral traits such as whether the short-lived token is invalidated, potential error conditions, or the exact nature of the long-lived token.

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 long, front-loads the core purpose, and contains no unnecessary words.

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?

The description explains the purpose and a prerequisite but lacks information about the return value or response format, which is important given the absence of an output schema. It is adequate but not fully complete.

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 input schema already has 100% coverage with a clear description of the single parameter. The tool description adds the context of what the exchange produces but does not add significant semantic value beyond the schema.

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 resources (short-lived token for long-lived token), distinguishing it from sibling tools like refresh_token and debug_token.

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?

It specifies a prerequisite (META_APP_ID and META_APP_SECRET must be configured), providing context for when to use the tool. However, it does not explicitly mention when not to use it or compare to alternatives like refresh_token.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mikusnuz/meta-ads-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server