Uber External Ads API MCP Server

get_campaigns

Retrieve advertising campaigns for a specific Uber ad account, with options to filter by status, limit results, and paginate through large datasets.

Instructions

Get campaigns for an ad account

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": {
      "ad_account_id": "<ad_account_id>"
    },
    "name": "get_campaigns"
  }
}

Input Schema

Name	Required	Description
`ad_account_id`	Yes	The ad account UUID
`auth_token`	No	Bearer token for authentication
`filters`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 24, 2025

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states a read operation ('Get') but lacks details on permissions, rate limits, pagination behavior, or response format. This leaves significant gaps for a tool that likely interacts with an API.

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 a single, efficient sentence with no wasted words. It is front-loaded and directly states the tool's purpose without unnecessary elaboration.

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

Completeness2/5

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

Given the complexity of a tool with 3 parameters, nested objects, no output schema, and no annotations, the description is insufficient. It does not cover behavioral aspects, response details, or usage context, making it incomplete for effective agent use.

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 description coverage is 67%, with parameters like 'ad_account_id' and 'filters' documented in the schema. The description adds no additional meaning beyond the schema, such as explaining filter usage or authentication context, but the schema provides adequate baseline coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('Get') and resource ('campaigns for an ad account'), making the purpose understandable. However, it does not distinguish this tool from its sibling 'get_campaign', which likely retrieves a single campaign, leaving some ambiguity about scope.

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

Usage Guidelines2/5

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

No explicit guidance is provided on when to use this tool versus alternatives like 'get_campaign' or other siblings. The description implies usage for retrieving multiple campaigns but offers no context on prerequisites, exclusions, or specific scenarios.

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

Deploy Server