Agent Central

DSP entities (live)

get_dsp_entities_live

Read-only

List Amazon-source DSP campaigns, ad groups, or targets through documented DSP v1 campaign-management read endpoints. Requires an explicit Amazon-Ads-AccountId DSP advertiser ID and returns factual source fields only; no DSP writes are exposed.

Input Schema

TableJSON Schema

Name	Required	Description
`states`	No	DSP targets only: optional Amazon DSP state filter values such as ENABLED. Campaign/ad-group state filters are not sent because Amazon does not document them for those list endpoints.
`next_token`	No	Amazon pagination token from a previous DSP list response.
`profile_id`	No	Numeric Amazon Ads profile ID. Optional when this API key has exactly one enabled Ads profile; agentcentral will default it. Call get_account_info for amazon_ads.enabled_profile_ids. Do not use the marketplace ID, tenant ID, or API key prefix.
`target_ids`	No	DSP targets only: filter targets by target ID. Target reads require target_ids or ad_group_ids because Amazon documents those as the bounded target-list filters.
`entity_type`	Yes	DSP entity family to list: campaign, ad_group, or target.
`max_results`	No	Maximum rows to request from Amazon (1-100).
`ad_group_ids`	No	Filter DSP ad groups by ad group ID, or targets by ad group ID.
`campaign_ids`	No	Filter DSP campaigns by campaign ID, or ad groups by campaign ID. DSP target list docs do not expose a campaign-id filter.
`target_types`	No	DSP targets only: optional target type filters such as AUDIENCE or LOCATION.
`include_raw_rows`	No	False returns compact rows. Default true.
`include_regional`	No	DSP campaigns/ad groups only: request cross-region records when Amazon supports includeRegional.
`include_diagnostics`	No	True may add expanded freshness diagnostics. Basic empty-result data-window diagnostics are included by default when available.
`amazon_ads_account_id`	Yes	Required Amazon-Ads-AccountId header value for DSP v1 campaign-management APIs. Amazon documents this as the Amazon DSP advertiser ID; discover it with get_dsp_advertisers_live.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`evidence`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 7, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true. The description reinforces this ('returns factual source fields only; no DSP writes are exposed') and adds the required-auth context (explicit advertiser ID), which is useful beyond the annotation defaults, though no return format or rate-limit details are offered.

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?

Two sentences that front-load the verb and resource, with the prerequisite and scope following. Efficient overall, though the second sentence packs several distinct facts (auth header, read-only scope) into one clause chain.

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?

An output schema exists, so return-value detail is unnecessary, and annotations carry the safety profile. The description supplies the key missing context—required advertiser ID and read-only scope—making it complete enough for correct invocation.

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 documents all 13 parameters in detail (including DSP-specific constraints like target_ids/ad_group_ids requirements). The description adds no parameter syntax or meaning beyond naming the account ID, so baseline 3 is appropriate.

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?

States a specific verb ('List') and resource ('Amazon-source DSP campaigns, ad groups, or targets') scoped to 'DSP v1 campaign-management read endpoints,' which cleanly separates it from siblings like get_dsp_performance (metrics) and get_dsp_advertisers_live (advertiser discovery).

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?

Clearly states the prerequisite (an explicit Amazon-Ads-AccountId DSP advertiser ID) and scopes usage to read endpoints with 'no DSP writes are exposed.' It does not, however, explicitly contrast when to use this versus entity-listing alternatives such as get_dsp_performance.

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

All Agent Central tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.