Skip to main content
Glama

list_brand_audit_watches

Read-onlyIdempotent

Lists your recurring brand-audit watches with domain, interval, webhook status, last-run time, and active state so you can review scheduled monitoring.

Instructions

Returns the caller's recurring brand-audit watches: watchId, domain, interval, webhook presence, last-run time, and active state. Owner-scoped. Read-only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_brand_audit_watches"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNoOutput verbosity.

Output Schema

NameRequiredDescriptionDefault
scoreYes
passedYes
partialNo
categoryYes
findingsYes
checkStatusNo
verdictWithheldNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.111.2
    • changedInput schema / properties / format / description
      Previous value: -"Output verbosity. Auto-detected if omitted."New value: +"Output verbosity."
  2. Changed2 schema fields changedv3.103.1
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / format
      Added value: +{
      +  "description": "Output verbosity. Auto-detected if omitted.",
      +  "enum": [
      +    "full",
      +    "compact"
      +  ],
      +  "type": "string"
      +}
  3. Changed1 schema field changedv3.98.1
    • addedOutput schema / properties / verdictWithheld
      Added value: +{
      +  "type": "boolean"
      +}
  4. Changed2 schema fields changedv3.54.0
    • addedOutput schema / properties / checkStatus
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / partial
      Added value: +{
      +  "type": "boolean"
      +}
  5. Addedv3.37.0
  6. Removedv3.31.1
  7. First observedv3.29.7

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, and the description's "Read-only" merely echoes that. The genuinely new context is "Owner-scoped", which tells the agent results are limited to the caller's own watches and cannot be widened; beyond that, nothing is said about empty results, ordering, or whether stale/inactive watches are included.

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 compact sentences, front-loaded with the return payload, followed by the two scoping facts that matter. No filler or repetition beyond the minor restatement of read-only.

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?

For a simple one-optional-parameter read tool with an output schema and full annotation coverage, the description covers purpose, scope and payload adequately. The only small gap is that it does not mention the compact/full format choice, which an agent must still discover from the schema.

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% and the single optional parameter (format: full|compact) is already documented with an enum, so the baseline is 3. The description never mentions verbosity at all, so it adds no meaning beyond the schema.

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?

The description states a specific verb and resource ("Returns the caller's recurring brand-audit watches") and enumerates the returned fields, so the agent knows exactly what comes back. The verb "Returns" plus "recurring watches" implicitly separates it from register_brand_audit_watch and delete_brand_audit_watch, though no sibling is named explicitly.

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 only implied: an agent can infer this is the listing counterpart to the register/delete watch tools. There is no explicit when-to-use statement, no exclusion, and no note about what to do when the list is empty or how to act on the returned watchIds.

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