Skip to main content
Glama

List monitors

list_monitors
Read-only

List the organization's brand monitors. Each monitor watches domains, trademark offices, app stores and search ads for conflicts with one brand. Only active assets are listed; archived ones are hidden, same as the dashboard.

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_monitors"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
monitorsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / monitors / items / properties / assets / items / properties / type / enum
      Previous value: -[
      -  "domain",
      -  "trademark",
      -  "app"
      -]New value: +[
      +  "domain",
      +  "trademark",
      +  "app",
      +  "search_ad"
      +]
  2. Changed2 schema fields changed
    • removedOutput schema / properties / monitors / items / properties / assets / items / properties / id
      Removed value: -{
      -  "type": "string"
      -}
    • changedOutput schema / properties / monitors / items / properties / assets / items / required
      Previous value: -[
      -  "id",
      -  "monitor_id",
      -  "type",
      -  "value",
      -  "status",
      -  "label",
      -  "scope",
      -  "cadence",
      -  "match_scope",
      -  "classes",
      -  "last_checked_at",
      -  "has_reference",
      -  "dashboard_url"
      -]New value: +[
      +  "monitor_id",
      +  "type",
      +  "value",
      +  "status",
      +  "label",
      +  "scope",
      +  "cadence",
      +  "match_scope",
      +  "classes",
      +  "last_checked_at",
      +  "has_reference",
      +  "dashboard_url"
      +]
  3. Changed3 schema fields changed
    • removedOutput schema / properties / monitors / items / properties / brand_context
      Removed value: -{
      -  "description": "The user's own background about the brand (what it sells, to whom and where, the companies, sites and partners it operates with); null when not set. Assessments read it; it never limits which subjects are found.",
      -  "type": [
      -    "string",
      -    "null"
      -  ]
      -}
    • addedOutput schema / properties / monitors / items / properties / brand_description
      Added value: +{
      +  "description": "The user's own background about the brand (what it sells, to whom and where, the companies, sites and partners it operates with); null when not set. Assessments read it; it never limits which subjects are found.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • changedOutput schema / properties / monitors / items / required
      Previous value: -[
      -  "id",
      -  "name",
      -  "status",
      -  "pause_reason",
      -  "next_scan_at",
      -  "brand_context",
      -  "dashboard_url",
      -  "assets"
      -]New value: +[
      +  "id",
      +  "name",
      +  "status",
      +  "pause_reason",
      +  "next_scan_at",
      +  "brand_description",
      +  "dashboard_url",
      +  "assets"
      +]
  4. Changed2 schema fields changed
    • addedOutput schema / properties / monitors / items / properties / brand_context
      Added value: +{
      +  "description": "The user's own background about the brand (what it sells, to whom and where, the companies, sites and partners it operates with); null when not set. Assessments read it; it never limits which subjects are found.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • changedOutput schema / properties / monitors / items / required
      Previous value: -[
      -  "id",
      -  "name",
      -  "status",
      -  "pause_reason",
      -  "next_scan_at",
      -  "dashboard_url",
      -  "assets"
      -]New value: +[
      +  "id",
      +  "name",
      +  "status",
      +  "pause_reason",
      +  "next_scan_at",
      +  "brand_context",
      +  "dashboard_url",
      +  "assets"
      +]
  5. Changed2 schema fields changed
    • addedOutput schema / properties / monitors / items / properties / assets / items / 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 / monitors / items / properties / assets / items / required
      Previous value: -[
      -  "id",
      -  "monitor_id",
      -  "type",
      -  "value",
      -  "status",
      -  "label",
      -  "scope",
      -  "cadence",
      -  "match_scope",
      -  "last_checked_at",
      -  "has_reference",
      -  "dashboard_url"
      -]New value: +[
      +  "id",
      +  "monitor_id",
      +  "type",
      +  "value",
      +  "status",
      +  "label",
      +  "scope",
      +  "cadence",
      +  "match_scope",
      +  "classes",
      +  "last_checked_at",
      +  "has_reference",
      +  "dashboard_url"
      +]
  6. First observed

TDQS

A4.2/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=false, so the safety profile is covered. The description still adds non-obvious behavior: archived monitors are silently omitted, matching the dashboard, which the agent could not learn from the schema or annotations.

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 short sentences, front-loaded with the verb and resource, then entity meaning, then the filtering caveat. Nothing is repeated from the title or annotations.

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?

With no parameters, an output schema handling return values, and annotations covering safety, the description only needs to convey scope and filtering — both are present. Pagination or ordering behavior is not mentioned, but the output schema likely covers the response shape.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline applies. The schema is empty and fully described, and no parameter claims are made or contradicted.

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 and resource ("List the organization's brand monitors") and then defines what a monitor is — watching domains, trademark offices, app stores and search ads for one brand. That definition alone separates it from siblings like list_matches, list_scans and list_takedowns, which enumerate other entity types.

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 implied by the resource name rather than stated: an agent can infer this is the read path for monitors and that create_monitor/update_monitor are the write paths, but the description never says so. There are no explicit exclusions or pointers to alternatives.

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