Skip to main content
Glama
affset

affset MCP server

by affset
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Create a zone

create_zone

Create a traffic-source zone to manage ad inventory and attribution. Preview the setup with a dry run, then pass confirm=true to activate the zone.

Instructions

Create a traffic-source zone in the current namespace. Requires a name; optional postback_url (where conversions are reported back — include {source_click_id}), site_url, traffic_back_url, user_email (publisher owner), and traffic_source_id (get_zone_url then renders that source's tracking template). Status is always active on create. Counts against the plan's zone limit (402 if exceeded). DRY-RUN by default; pass confirm=true to apply.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesZone display name (traffic source / placement).
confirmNofalse = dry-run preview (default). true = create the zone.
site_urlNoOptional site / inventory URL.
user_emailNoOptional publisher email to own this zone (owner/manager only).
postback_urlNoS2S postback URL for the traffic source. Should include {source_click_id} so conversions can be attributed back to the source click.
traffic_back_urlNoOptional traffic-back / fallback URL when no campaign can serve.
traffic_source_idNoTraffic source to link (see list_traffic_sources). Must be a source in this namespace. get_zone_url/get_tracking_link then render its tracking template.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.0
    • addedInput schema / properties / traffic_source_id
      Added value: +{
+  "description": "Traffic source to link (see list_traffic_sources). Must be a source in this namespace. get_zone_url/get_tracking_link then render its tracking template.",
+  "minLength": 1,
+  "type": "string"
+}
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

The description discloses critical behaviors not visible in annotations: DRY-RUN by default, confirm=true required to apply, status always active on create, and the plan's zone limit error (402). These are valuable operational details that exceed what annotations provide.

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?

Three dense sentences that front-load the purpose, then list required/optional parameters, then state the most important behavioral facts. No wasted words; every sentence earns its place.

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?

For a 7-parameter creation tool with no output schema, the description covers the required input, key optional parameters, default dry-run behavior, confirmation requirement, resulting status, and quota error. This is sufficient for an agent to invoke it safely and correctly.

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 every parameter. The description mostly restates the optional parameters and adds minor context like postback_url being for conversions and traffic_source_id influencing get_zone_url, but it does not significantly add meaning beyond the schema.

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 names a specific verb and resource: 'Create a traffic-source zone in the current namespace.' It clearly distinguishes this from sibling tools like update_zone, list_zones, and create_campaign by specifying the resource type and scope.

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?

The description gives clear context: creating a new zone, requiring a name, and linking an optional traffic source. It does not explicitly state when not to use it or mention alternatives, but the context is enough for an agent to select it over update_zone or create_campaign.

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