Skip to main content
Glama
shinypebble

microsoft-ads-mcp

by shinypebble

check_first_page_bids

Read-only

Identify keywords with bids below the estimated first-page bid. Compare current bid to first-page estimate to find under-bid keywords, helping diagnose low impressions before activating a campaign.

Instructions

Flag keywords whose bid is below the estimated first-page bid ("Below first page bid").

This is the API-driven version of the delivery state the UI shows as "Below first page bid". For each keyword in the ad group it looks up the Keyword Planner first-page bid estimate (at the keyword's own match type) and compares it against the keyword's effective bid -- the keyword's own bid, or the ad group's default bid when the keyword has none. The result lists the under-bid keywords first (largest shortfall first) with each one's current_bid, estimated_first_page_bid, and bid_source, plus counts. Use it when diagnosing low impressions, or before activating a campaign, to find keywords that won't reach the first page at their current bid.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
languageNoLanguage name for the estimate, e.g. "English" (optional).
ad_group_idYesThe ad group whose keywords to check.
campaign_idYesThe parent campaign id -- required to read the ad group's default bid, which keywords without their own bid inherit.
location_idsNoMicrosoft location ids to scope demand to; the estimate defaults to the United States ("190") when omitted.
target_positionNo"FirstPage" (default), "MainLine", or "MainLine1" (top ad slot).FirstPage

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
keywordsNo
ad_group_idYes
currency_codeNo
target_positionYes
keywords_checkedYes
undetermined_countYes
ad_group_default_bidNo
below_first_page_countYes
Behavior5/5

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

The description explains the internal logic: looks up Keyword Planner first-page bid estimate, compares it to effective bid, and lists under-bid keywords with details. This adds significant value beyond the readOnlyHint annotation.

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 well-structured, starting with the core purpose, then explaining the algorithm and output. Every sentence adds value without unnecessary verbosity.

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

Completeness5/5

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

Given the presence of an output schema, the description adequately covers the purpose, usage, and behavioral details. It mentions the result structure (under-bid keywords with fields and counts), making it complete.

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?

Schema coverage is 100%, so baseline is 3. However, the description adds context on how parameters like campaign_id are used (to read the ad group's default bid), which goes beyond the schema descriptions.

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 tool's purpose: 'Flag keywords whose bid is below the estimated first-page bid.' It is specific and distinguishes from sibling tools by focusing on a unique diagnostic action.

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

Usage Guidelines5/5

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

Explicit usage guidance is provided: 'Use it when diagnosing low impressions, or before activating a campaign, to find keywords that won't reach the first page at their current bid.' This clearly indicates when to use the tool.

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/shinypebble/microsoft-ads-mcp'

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