Skip to main content
Glama

Add asset

add_asset

Add an asset to a monitor: an official domain to watch for conflicting registrations, a mark text for trademark office filings, a brand keyword for app store listings, or a brand name for ads on US Google and Bing searches. This is confirmed work: confirm true records that the user approved the exact type, value, config and reference choice, because the first scan is scheduled as soon as the asset exists and archiving (dashboard-only) only stops future scans, it does not undo a scan that already completed. Required config per type: domain needs config.brand, trademark needs config.offices (subset of US, EM; classes optional, Nice 1-45), app needs config.stores (subset of google_play, app_store), search_ad takes config.engines (subset of google, bing; both when omitted). Domain assets also need an explicit reference choice (capture, upload or skip); trademark and app accept an optional upload staged with prepare_asset_upload, and search_ad takes no reference. A capture always goes through preview_domain: its capture_token makes the stored baseline exactly the render the user approved, and the response includes that screenshot as image content. When the preview produced no screenshot (captured false), upload or skip are the choices; a capture_token from such a preview stores only the site icon. site_result carries the probe outcome recorded at preview time. For domain assets, the response's match_scope reports the matching scope: 'distinctive' names are matched across TLDs while 'generic' common terms are only watched on the asset's own suffix. On an active monitor the first scan starts right away (list_scans shows it); next_scan_at reports the next scheduled scan, null while that first scan is still running or the monitor is paused. Errors name the cause: invalid input, plan limit reached, or a duplicate already watched by the monitor.

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": {
      "monitor_id": "<monitor_id>",
      "confirm": "<confirm>",
      "type": "<type>",
      "value": "<value>"
    },
    "name": "add_asset"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesAsset type: domain, trademark, app or search_ad.
valueYesWhat to watch: the official domain for type domain (e.g. "acme.com"), the mark or brand text for trademark, the brand keyword for app, the brand name searched on Google and Bing for search_ad.
configNoType-specific options: brand (required for domain), offices (required for trademark: subset of US, EM), classes (optional Nice classes 1-45, trademark only), stores (required for app: subset of google_play, app_store), engines (search_ad only: subset of google, bing; both when omitted).
confirmYesRequired. true records that the user explicitly confirmed the exact asset: its type, value, config and reference choice, knowing the first scan is scheduled right away.
referenceNoVisual baseline. Required for domain: capture stores the render approved in preview_domain via its capture_token, upload attaches an image staged with prepare_asset_upload, skip stores no baseline (upload or skip are the choices when the preview produced no screenshot, captured false). Optional for trademark and app; only upload applies there (mark image or app icon). search_ad takes none.
monitor_idYesMonitor id from list_monitors or create_monitor.

Output Schema

NameRequiredDescriptionDefault
assetYes
site_resultYes
next_scan_atYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • changedInput schema / properties / config / description
      Previous value: -"Type-specific options: brand (required for domain), offices (required for trademark: subset of US, EM), classes (optional Nice classes 1-45, trademark only), stores (required for app: subset of google_play, app_store)."New value: +"Type-specific options: brand (required for domain), offices (required for trademark: subset of US, EM), classes (optional Nice classes 1-45, trademark only), stores (required for app: subset of google_play, app_store), engines (search_ad only: subset of google, bing; both when omitted)."
    • addedInput schema / properties / config / properties / engines
      Added value: +{
      +  "items": {
      +    "enum": [
      +      "google",
      +      "bing"
      +    ],
      +    "type": "string"
      +  },
      +  "maxItems": 2,
      +  "type": "array"
      +}
    • changedInput schema / properties / reference / description
      Previous value: -"Visual baseline. Required for domain: capture stores the render approved in preview_domain via its capture_token, upload attaches an image staged with prepare_asset_upload, skip stores no baseline (upload or skip are the choices when the preview produced no screenshot, captured false). Optional for trademark and app; only upload applies there (mark image or app icon)."New value: +"Visual baseline. Required for domain: capture stores the render approved in preview_domain via its capture_token, upload attaches an image staged with prepare_asset_upload, skip stores no baseline (upload or skip are the choices when the preview produced no screenshot, captured false). Optional for trademark and app; only upload applies there (mark image or app icon). search_ad takes none."
    • changedInput schema / properties / type / description
      Previous value: -"Asset type: domain, trademark or app."New value: +"Asset type: domain, trademark, app or search_ad."
    • changedInput schema / properties / type / enum
      Previous value: -[
      -  "domain",
      -  "trademark",
      -  "app"
      -]New value: +[
      +  "domain",
      +  "trademark",
      +  "app",
      +  "search_ad"
      +]
    • changedInput schema / properties / value / description
      Previous value: -"What to watch: the official domain for type domain (e.g. \"acme.com\"), the mark or brand text for trademark, the brand keyword for app."New value: +"What to watch: the official domain for type domain (e.g. \"acme.com\"), the mark or brand text for trademark, the brand keyword for app, the brand name searched on Google and Bing for search_ad."
    • changedOutput schema / properties / asset / properties / type / enum
      Previous value: -[
      -  "domain",
      -  "trademark",
      -  "app"
      -]New value: +[
      +  "domain",
      +  "trademark",
      +  "app",
      +  "search_ad"
      +]
  2. Changed2 schema fields changed
    • removedOutput schema / properties / asset / properties / id
      Removed value: -{
      -  "type": "string"
      -}
    • changedOutput schema / properties / asset / required
      Previous value: -[
      -  "id",
      -  "monitor_id",
      -  "type",
      -  "value",
      -  "status",
      -  "label",
      -  "scope",
      -  "cadence",
      -  "match_scope",
      -  "classes",
      -  "last_checked_at",
      -  "has_reference",
      -  "dashboard_url",
      -  "reference_stored"
      -]New value: +[
      +  "monitor_id",
      +  "type",
      +  "value",
      +  "status",
      +  "label",
      +  "scope",
      +  "cadence",
      +  "match_scope",
      +  "classes",
      +  "last_checked_at",
      +  "has_reference",
      +  "dashboard_url",
      +  "reference_stored"
      +]
  3. Changed3 schema fields changed
    • changedInput schema / properties / reference / description
      Previous value: -"Visual baseline. Required for domain: capture stores the render approved in preview_domain via its capture_token, upload attaches an image staged with prepare_asset_upload, skip stores no baseline (the remaining choice when the preview rendered nothing, captured false). Optional for trademark and app; only upload applies there (mark image or app icon)."New value: +"Visual baseline. Required for domain: capture stores the render approved in preview_domain via its capture_token, upload attaches an image staged with prepare_asset_upload, skip stores no baseline (upload or skip are the choices when the preview produced no screenshot, captured false). Optional for trademark and app; only upload applies there (mark image or app icon)."
    • addedOutput schema / properties / asset / properties / classes
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {
      +        "type": "number"
      +      },
      +      "type": "array"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Nice classes of a trademark asset, empty when none were set; null for other types. Classes inform the assessment and never limit which filings are found."
      +}
    • changedOutput schema / properties / asset / required
      Previous value: -[
      -  "id",
      -  "monitor_id",
      -  "type",
      -  "value",
      -  "status",
      -  "label",
      -  "scope",
      -  "cadence",
      -  "match_scope",
      -  "last_checked_at",
      -  "has_reference",
      -  "dashboard_url",
      -  "reference_stored"
      -]New value: +[
      +  "id",
      +  "monitor_id",
      +  "type",
      +  "value",
      +  "status",
      +  "label",
      +  "scope",
      +  "cadence",
      +  "match_scope",
      +  "classes",
      +  "last_checked_at",
      +  "has_reference",
      +  "dashboard_url",
      +  "reference_stored"
      +]
  4. Changed1 schema field changed
    • changedOutput schema / properties / site_result / anyOf
      Previous value: -[
      -  {
      -    "enum": [
      -      "ok",
      -      "unreachable",
      -      "blocked"
      -    ],
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "ok",
      +      "http_error",
      +      "unreachable",
      +      "blocked"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  5. Changed2 schema fields changed
    • changedInput schema / properties / config / description
      Previous value: -"Type-specific options: brand (required for domain), offices (required for trademark: subset of US, EM, WO), classes (optional Nice classes 1-45, trademark only), stores (required for app: subset of google_play, app_store)."New value: +"Type-specific options: brand (required for domain), offices (required for trademark: subset of US, EM), classes (optional Nice classes 1-45, trademark only), stores (required for app: subset of google_play, app_store)."
    • changedInput schema / properties / reference / description
      Previous value: -"Visual baseline. Required for domain: capture stores the render approved in preview_domain via its capture_token, upload attaches an image staged with prepare_asset_upload, skip stores no baseline (use it when the preview rendered nothing, captured false). Optional for trademark and app; only upload applies there (mark image or app icon)."New value: +"Visual baseline. Required for domain: capture stores the render approved in preview_domain via its capture_token, upload attaches an image staged with prepare_asset_upload, skip stores no baseline (the remaining choice when the preview rendered nothing, captured false). Optional for trademark and app; only upload applies there (mark image or app icon)."
  6. Changed1 schema field changed
    • changedInput schema / properties / confirm / description
      Previous value: -"Required. Set true only after the user has explicitly confirmed the exact asset: its type, value, config and reference choice, knowing the first scan is scheduled right away."New value: +"Required. true records that the user explicitly confirmed the exact asset: its type, value, config and reference choice, knowing the first scan is scheduled right away."
  7. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond annotations, it discloses that the first scan is scheduled immediately, that archiving only stops future scans and cannot undo a completed scan, and how capture_token binds the baseline to the approved preview. It also explains match_scope, site_result, next_scan_at, and error causes, giving the agent mutation side effects and result interpretation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is front-loaded and content-rich, but it is a long dense paragraph that repeats schema-described config, confirm, and reference rules while combining many separate facts. For a complex tool the length is defensible, but the repetition and run-on structure keep it from being tight.

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 six-parameter mutation with four asset types, nested config, and an output schema, it covers purpose, prerequisites, side effects, reference rules, scan timing, and errors. Because an output schema exists, it need not explain every return field; what it does explain is complete enough to call correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description adds useful semantics for reference (captured false means upload or skip are the choices; a captureToken from such a preview stores only the site icon) and for search_ad taking no reference. It also restates type-specific config requirements already in the schema, so it is not a full 5.

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 opening sentence names a specific verb and resource and enumerates all four asset types, so an agent can identify it as the creation tool for monitor assets. It also references preview_domain and prepare_asset_upload for prerequisite steps, which helps separate this call from those preparation tools.

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?

It states the key preconditions ('confirmed work', confirm true recording user approval) and gives explicit choices per type: capture/upload/skip for domain, optional upload for trademark and app, and none for search_ad. It lacks a direct 'do not use this when...' exclusion, but the alternative sub-tools and conditions are clear.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources