Skip to main content
Glama
Sign In
Apple Ads MCP

Apple Ads MCP

by AppVisionOS
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

campaigns_find

Search and filter Apple Ads campaigns using a flexible selector with conditions, sorting, and pagination.

Instructions

Search campaigns with a selector — supports conditions (EQUALS/IN/CONTAINS/...), orderBy, and pagination.

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": {
      "selector": "<selector>"
    },
    "name": "campaigns_find"
  }
}

Input Schema

NameRequiredDescriptionDefault
selectorYesSelector object for /find endpoints. Combine conditions / fields / orderBy / pagination.
orgIdNoOverride the org (account) for this call. Defaults to ASA_ORG_ID. Use the `org_acls` tool to discover orgIds.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

No annotations, but the description states 'search' which implies read-only. It details supported operations but doesn't explicitly confirm no side effects.

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?

Single sentence, front-loaded with key info, no fluff.

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

Completeness4/5

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

Covers purpose and key features. No output schema, so description could mention return type, but 'search campaigns' implies a list. Nested objects are addressed.

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 coverage is 100%, so the schema already describes parameters. The description adds context that the selector supports conditions/orderBy/pagination but doesn't go beyond the schema's detail.

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 searches campaigns using a selector with conditions, orderBy, and pagination. It distinguishes from siblings like campaigns_list and campaigns_get.

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?

Usage is implied (search with filters/sorting/pagination) but no explicit when-to-use or alternatives mentioned. Sibling tools like campaigns_list exist for simpler listing.

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