Skip to main content
Glama

Market Brew

List prioritized optimization tasks

list_top_tasks
Read-onlyIdempotent

Use this when the user asks to list prioritized optimization tasks. Returns only data visible to the linked Market Brew account.

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

Input Schema

NameRequiredDescriptionDefault
queryNoOptional filters: websiteId, serverHost, startDate, endDate, taskTitle, sortBy, sortDir, offset, and pageSize.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • removedInput schema / properties / query / properties / endDate / $ref
      Removed value: -"#/properties/query/properties/startDate"
    • addedInput schema / properties / query / properties / endDate / format
      Added value: +"date"
    • addedInput schema / properties / query / properties / endDate / pattern
      Added value: +"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))$"
    • addedInput schema / properties / query / properties / endDate / type
      Added value: +"string"
    • addedInput schema / properties / query / properties / startDate / pattern
      Added value: +"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))$"
    • changedInput schema / properties / query / properties / websiteId / anyOf
      Previous value: -[
      -  {
      -    "exclusiveMinimum": 0,
      -    "maximum": 9007199254740991,
      -    "minimum": -9007199254740991,
      -    "type": "integer"
      -  },
      -  {
      -    "pattern": "^[1-9][0-9]{0,17}$",
      -    "type": "string"
      -  }
      -]New value: +[
      +  {
      +    "exclusiveMinimum": 0,
      +    "maximum": 9007199254740991,
      +    "type": "integer"
      +  },
      +  {
      +    "pattern": "^[1-9][0-9]{0,17}$",
      +    "type": "string"
      +  }
      +]
  2. Changed3 schema fields changed
    • changedInput schema / properties / query / additionalProperties
      Previous value: -{
      -  "type": [
      -    "string",
      -    "number",
      -    "boolean",
      -    "null"
      -  ]
      -}New value: +false
    • changedInput schema / properties / query / description
      Previous value: -"Optional filters: websiteId, serverHost, workspaceId, startDate, endDate, taskTitle, sortBy, sortDir, offset, and pageSize."New value: +"Optional filters: websiteId, serverHost, startDate, endDate, taskTitle, sortBy, sortDir, offset, and pageSize."
    • addedInput schema / properties / query / properties
      Added value: +{
      +  "endDate": {
      +    "$ref": "#/properties/query/properties/startDate"
      +  },
      +  "offset": {
      +    "maximum": 1000000,
      +    "minimum": 0,
      +    "type": "integer"
      +  },
      +  "pageSize": {
      +    "maximum": 200,
      +    "minimum": 1,
      +    "type": "integer"
      +  },
      +  "serverHost": {
      +    "maxLength": 253,
      +    "type": "string"
      +  },
      +  "sortBy": {
      +    "maxLength": 80,
      +    "type": "string"
      +  },
      +  "sortDir": {
      +    "enum": [
      +      "asc",
      +      "desc"
      +    ],
      +    "type": "string"
      +  },
      +  "startDate": {
      +    "format": "date",
      +    "type": "string"
      +  },
      +  "taskTitle": {
      +    "maxLength": 2048,
      +    "type": "string"
      +  },
      +  "websiteId": {
      +    "anyOf": [
      +      {
      +        "exclusiveMinimum": 0,
      +        "maximum": 9007199254740991,
      +        "minimum": -9007199254740991,
      +        "type": "integer"
      +      },
      +      {
      +        "pattern": "^[1-9][0-9]{0,17}$",
      +        "type": "string"
      +      }
      +    ]
      +  }
      +}
  3. First observed

TDQS

B3.4/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, so the safety profile is covered. The description does add one genuinely useful behavioral fact beyond that: results are scoped to what the linked Market Brew account can see. It says nothing about ordering defaults, pagination limits, or result volume.

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 short sentences, trigger condition front-loaded, no filler or repetition of schema detail. It is appropriately sized, though the second sentence about account visibility is somewhat disconnected from the first.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only list tool with full schema coverage and rich filter documentation, the description is adequate but leaves gaps: what 'prioritized' ordering means, whether results are paginated, and how it relates to the sibling list_tasks are all unaddressed.

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 nested query object enumerates every filter (websiteId, serverHost, dates, taskTitle, sort, offset, pageSize), so the schema carries parameter meaning. The description adds no semantics beyond that, which is the expected baseline when coverage is complete.

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 and resource ('list prioritized optimization tasks'), so an agent knows the operation is a read of ranked tasks. It stops short of distinguishing this from the sibling 'list_tasks', so an agent cannot tell without opening schemas whether this is a filtered subset or a different ordering.

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?

Gives a trigger condition ('when the user asks to list prioritized optimization tasks'), which is essentially a restatement of the name and title. There is no when-not guidance and no named alternative such as list_tasks or get_top_task_metrics, so selection between close siblings is left to inference.

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