Skip to main content
Glama
ZLeventer

google-ads-mcp

gads_list_rsas

List responsive search ads with headlines, descriptions, Ad Strength rating, and approval status. Filter by campaign or ad group to review ad performance and optimize ad copy.

Instructions

List Responsive Search Ads with all headlines, descriptions, Ad Strength rating, and approval status. Filter by campaign or ad group.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
customer_idNoOverride GOOGLE_ADS_CUSTOMER_ID for this call
campaign_idNoFilter to a specific campaign ID
ad_group_idNoFilter to a specific ad group ID
limitNo

Implementation Reference

  • src/index.ts:135-140 (registration)
    Tool 'gads_list_rsas' is registered with the MCP server using listRsasSchema and the listRsas handler.
    server.tool(
      "gads_list_rsas",
      "List Responsive Search Ads with all headlines, descriptions, Ad Strength rating, and approval status. Filter by campaign or ad group.",
      listRsasSchema,
      async (args) => { try { return ok(await listRsas(args)); } catch (e) { return err(e); } }
    );
  • Schema definition for gads_list_rsas: accepts optional customer_id, campaign_id, ad_group_id filters and a limit (default 50, max 10000).
    export const listRsasSchema = {
      customer_id: z.string().optional().describe("Override GOOGLE_ADS_CUSTOMER_ID for this call"),
      campaign_id: z.string().optional().describe("Filter to a specific campaign ID"),
      ad_group_id: z.string().optional().describe("Filter to a specific ad group ID"),
      limit: z.number().int().positive().max(10000).default(50),
    };
  • Handler function that queries Google Ads for Responsive Search Ads with headlines, descriptions, ad strength, approval status, filtered by campaign/ad group.
    export async function listRsas(args: z.infer<z.ZodObject<typeof listRsasSchema>>) {
      const customer = getCustomer(args.customer_id);
      const adGroupClause = args.ad_group_id ? `AND ad_group.id = ${args.ad_group_id}` : "";
      const campaignClause = args.campaign_id ? `AND campaign.id = ${args.campaign_id}` : "";
      const rows = await customer.query(`
        SELECT
          campaign.id,
          campaign.name,
          ad_group.id,
          ad_group.name,
          ad_group_ad.ad.id,
          ad_group_ad.ad.responsive_search_ad.headlines,
          ad_group_ad.ad.responsive_search_ad.descriptions,
          ad_group_ad.ad.final_urls,
          ad_group_ad.ad_strength,
          ad_group_ad.policy_summary.approval_status,
          ad_group_ad.status
        FROM ad_group_ad
        WHERE ad_group_ad.ad.type = 'RESPONSIVE_SEARCH_AD'
          ${campaignClause}
          ${adGroupClause}
        LIMIT ${args.limit}
      `);
      return { rowCount: rows.length, rows };
    }
  • The getCustomer helper used by listRsas to create a Google Ads client.
    import { GoogleAdsApi, Customer } from "google-ads-api";
Behavior2/5

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

No annotations are provided, so the description should disclose behavioral traits. It describes the output fields but does not mention that the operation is read-only, nor does it cover authentication requirements, rate limits, or potential side effects. The description is insufficient to fully inform the agent about the tool's behavior.

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?

The description is a single sentence that is front-loaded with the primary action ('List Responsive Search Ads') and conveys the key features concisely. It avoids unnecessary detail, making it efficient for an AI agent to parse.

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 lists the fields returned (headlines, descriptions, Ad Strength, approval status) but does not explain pagination, ordering, or the absence of an output schema. For a tool with a `limit` parameter, pagination details would enhance completeness. The description is adequate but not thorough.

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 provides descriptions for 3 out of 4 parameters (customer_id, campaign_id, ad_group_id, limit) with coverage at 75%. The tool description only repeats the filtering concept from the schema, adding no new semantic meaning. Baseline score of 3 is appropriate given the schema coverage.

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 'List Responsive Search Ads' with specific fields (headlines, descriptions, Ad Strength rating, approval status) and filtering options. It effectively distinguishes from sibling tools like gads_list_assets or gads_rsa_asset_performance by focusing on RSAs.

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 mentions filtering by campaign or ad group, which gives some usage context, but it does not explicitly state when to use this tool versus alternatives like gads_campaign_assets or gads_rsa_asset_performance. The usage guidelines are implied rather than explicit.

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/ZLeventer/google-ads-mcp'

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