Skip to main content
Glama

List opportunities

list_opportunities
Read-onlyIdempotent

The brand's opportunity inbox: content, readiness, source, traffic, and coverage gaps, each with its score, AI search demand, stage (now, in_flight, watching, won), and assignee, plus stage counts for the active inbox (counts.ready_to_win: watching items whose gap has closed). Start here to find an opportunity_id, read it with get_opportunity, and change it with act_on_opportunity or update_opportunities.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindNoOptional filter.
viewNoDefaults to active.
brandYesBrand or study: its ID from list_brands, or its name (exact or a unique prefix).
limitNoRows per page. Defaults to 25, max 100. A page may hold fewer rows to stay within the response size; follow next_cursor.
stageNoOptional filter.
cursorNonext_cursor from the previous page. Leave out for the first page.
segmentNoOptional segment ID or name. get_brand_settings lists the brand's segments.
assigneeNoOptional: me, or a member ID (none is not accepted here). No tool lists members: take an ID from an opportunity's assignee.member_id.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYes
generated_atYesRFC 3339 time the response was made.
schema_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / assignee / description
      Previous value: -"Optional: me, or a member ID."New value: +"Optional: me, or a member ID (none is not accepted here). No tool lists members: take an ID from an opportunity's assignee.member_id."
  2. Changed5 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / brand / minLength
      Added value: +1
    • changedInput schema / properties / cursor / description
      Previous value: -"next_cursor from the previous page."New value: +"next_cursor from the previous page. Leave out for the first page."
    • changedInput schema / properties / limit / description
      Previous value: -"Rows per page. Defaults to 25, max 100."New value: +"Rows per page. Defaults to 25, max 100. A page may hold fewer rows to stay within the response size; follow next_cursor."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "data": {
      +      "additionalProperties": false,
      +      "properties": {
      +        "brand": {
      +          "additionalProperties": false,
      +          "properties": {
      +            "id": {
      +              "type": "string"
      +            },
      +            "name": {
      +              "type": "string"
      +            },
      +            "url": {
      +              "description": "The brand's website, or empty when none is set.",
      +              "type": "string"
      +            }
      +          },
      +          "required": [
      +            "id",
      +            "name",
      +            "url"
      +          ],
      +          "type": "object"
      +        },
      +        "counts": {
      +          "additionalProperties": false,
      +          "properties": {
      +            "in_flight": {
      +              "type": "integer"
      +            },
      +            "now": {
      +              "type": "integer"
      +            },
      +            "ready_to_win": {
      +              "description": "Watching items whose gap has closed; move them to won.",
      +              "type": "integer"
      +            },
      +            "watching": {
      +              "type": "integer"
      +            },
      +            "won": {
      +              "description": "Won this month.",
      +              "type": "integer"
      +            }
      +          },
      +          "required": [
      +            "now",
      +            "in_flight",
      +            "watching",
      +            "won",
      +            "ready_to_win"
      +          ],
      +          "type": "object"
      +        },
      +        "opportunities": {
      +          "items": {
      +            "additionalProperties": false,
      +            "properties": {
      +              "assignee": {
      +                "additionalProperties": false,
      +                "properties": {
      +                  "member_id": {
      +                    "type": "string"
      +                  },
      +                  "name": {
      +                    "type": "string"
      +                  }
      +                },
      +                "required": [
      +                  "member_id",
      +                  "name"
      +                ],
      +                "type": [
      +                  "null",
      +                  "object"
      +                ]
      +              },
      +              "comment_count": {
      +                "type": "integer"
      +              },
      +              "dismissed_at": {
      +                "type": "string"
      +              },
      +              "found_at": {
      +                "type": "string"
      +              },
      +              "id": {
      +                "type": "string"
      +              },
      +              "kind": {
      +                "description": "content_gap, readiness, source_gap, traffic_gap, or coverage_gap.",
      +                "type": "string"
      +              },
      +              "monthly_ai_searches": {
      +                "type": [
      +                  "null",
      +                  "integer"
      +                ]
      +              },
      +              "score": {
      +                "description": "0-100 priority.",
      +                "type": "integer"
      +              },
      +              "segment": {
      +                "additionalProperties": false,
      +                "properties": {
      +                  "id": {
      +                    "type": "string"
      +                  },
      +                  "name": {
      +                    "type": "string"
      +                  }
      +                },
      +                "required": [
      +                  "id",
      +                  "name"
      +                ],
      +                "type": [
      +                  "null",
      +                  "object"
      +                ]
      +              },
      +              "signal": {
      +                "description": "Why it matters now.",
      +                "type": "string"
      +              },
      +              "snoozed_until": {
      +                "type": "string"
      +              },
      +              "stage": {
      +                "description": "now, in_flight, watching, or won.",
      +                "type": "string"
      +              },
      +              "stage_changed_at": {
      +                "type": "string"
      +              },
      +              "title": {
      +                "type": "string"
      +              }
      +            },
      +            "required": [
      +              "id",
      +              "kind",
      +              "stage",
      +              "title",
      +              "signal",
      +              "segment",
      +              "monthly_ai_searches",
      +              "score",
      +              "assignee",
      +              "found_at",
      +              "stage_changed_at",
      +              "snoozed_until",
      +              "dismissed_at",
      +              "comment_count"
      +            ],
      +            "type": "object"
      +          },
      +          "type": "array"
      +        },
      +        "pagination": {
      +          "additionalProperties": false,
      +          "properties": {
      +            "next_cursor": {
      +              "description": "Pass as cursor to get the next page; empty on the last page.",
      +              "type": "string"
      +            },
      +            "total": {
      +              "description": "Items across all pages; null when not counted.",
      +              "type": [
      +                "null",
      +                "integer"
      +              ]
      +            }
      +          },
      +          "required": [
      +            "next_cursor",
      +            "total"
      +          ],
      +          "type": "object"
      +        }
      +      },
      +      "required": [
      +        "brand",
      +        "counts",
      +        "opportunities",
      +        "pagination"
      +      ],
      +      "type": "object"
      +    },
      +    "generated_at": {
      +      "description": "RFC 3339 time the response was made.",
      +      "type": "string"
      +    },
      +    "schema_version": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "schema_version",
      +    "generated_at",
      +    "data"
      +  ],
      +  "type": "object"
      +}
  3. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive behavior, so the bar is lower. The description adds context annotations cannot: the returned fields, stage vocabulary, and the semantics of counts.ready_to_win (watching items whose gap has closed). It omits anything about auth or rate limits, but adds real behavioral value over the structured fields.

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?

Two sentences, front-loaded with what the tool returns and then the routing advice. The first sentence is a dense run-on that packs fields, stages and counts together, but there is no filler.

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?

An output schema exists, so return shape need not be re-explained; the 8-parameter schema is fully described. Combined with the explicit follow-up workflow, an agent has enough to call this correctly, though nothing covers the active/view default interaction or pagination caveats.

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 all filtering params (kind, view, stage, segment, assignee, limit, cursor) are documented in the schema itself. The description restates the stage values but adds no syntax, defaults, or interactions beyond the schema, so baseline 3 applies.

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 (list) and resource (the brand's opportunity inbox) and enumerates its contents: content, readiness, source, traffic and coverage gaps with score, demand, stage and assignee. It also names sibling tools (get_opportunity, act_on_opportunity, update_opportunities), so an agent can distinguish it without opening the schema.

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?

Explicitly frames the tool as the entry point: 'Start here to find an opportunity_id, read it with get_opportunity, and change it with act_on_opportunity or update_opportunities.' That is a clear workflow with named alternatives. It stops short of stating when-not to use it (e.g., when the ID is already known).

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