Skip to main content
Glama

adpanel_ingest_brand_matrix

Ingest a brand matrix envelope to register brand assets, labels, roles, and routing tags with the AdPanel gateway so source assets can be routed and managed.

Instructions

Ingest a brand matrix envelope and register source assets with the AdPanel routing gateway.

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": {
      "brandName": "<brandName>",
      "sourceAssets": "<sourceAssets>"
    },
    "name": "adpanel_ingest_brand_matrix"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNoOptional routing tags
brandNameYesHuman-readable brand label for routing
sourceAssetsYesOrdered list of brand source assets
matrixVersionNoBrand matrix schema version1.0

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. 'Ingest' and 'register' imply a write/mutation against a routing gateway, but the description says nothing about idempotency, duplicate handling, required permissions, validation failures, or whether registered assets are persisted or merely routed — all material for a mutation tool with zero annotation coverage.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though the terseness contributes to the gaps in usage and behavioral disclosure rather than offsetting them.

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?

For a four-parameter mutation tool with no annotations and no output schema, the description should disclose side effects and expected outcome. Instead it only restates the operation, leaving the agent without enough context to call it confidently in a workflow.

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 100%, with brandName, sourceAssets (including nested url/role/label), tags, and matrixVersion all documented in the schema itself. The description adds no semantics beyond the schema, so the baseline 3 applies.

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?

States a specific verb ('Ingest') and resource ('brand matrix envelope') plus a second action ('register source assets with the AdPanel routing gateway'), so the agent knows this is a registration/write operation. It does not, however, contrast itself with the sibling tools (adpanel_orchestrate_cinematic_timeline, adpanel_synthesize_broadcast_asset), so differentiation is left to inference.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives or when not to call it. The agent must guess whether this is the entry point for a brand workflow or a follow-up step.

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