Skip to main content
Glama

Market Brew

List current Ranking Sensor tasks

list_tasks
Read-onlyIdempotent

Use this when the user asks to list current Ranking Sensor 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_tasks"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoOptional filters: websiteId, webpageId, boostFactorId, serverHost, workspaceId, rankingSensorId, snapshotId, startDate, endDate, taskTitle, sortBy, sortDir, offset, and pageSize.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / query / additionalProperties
      Previous value: -{
      -  "type": [
      -    "string",
      -    "number",
      -    "boolean",
      -    "null"
      -  ]
      -}New value: +false
    • addedInput schema / properties / query / properties
      Added value: +{
      +  "boostFactorId": {
      +    "$ref": "#/properties/query/properties/websiteId"
      +  },
      +  "endDate": {
      +    "$ref": "#/properties/query/properties/startDate"
      +  },
      +  "offset": {
      +    "maximum": 1000000,
      +    "minimum": 0,
      +    "type": "integer"
      +  },
      +  "pageSize": {
      +    "maximum": 200,
      +    "minimum": 1,
      +    "type": "integer"
      +  },
      +  "rankingSensorId": {
      +    "$ref": "#/properties/query/properties/websiteId"
      +  },
      +  "serverHost": {
      +    "maxLength": 253,
      +    "type": "string"
      +  },
      +  "snapshotId": {
      +    "$ref": "#/properties/query/properties/websiteId"
      +  },
      +  "sortBy": {
      +    "maxLength": 80,
      +    "type": "string"
      +  },
      +  "sortDir": {
      +    "enum": [
      +      "asc",
      +      "desc"
      +    ],
      +    "type": "string"
      +  },
      +  "startDate": {
      +    "format": "date",
      +    "type": "string"
      +  },
      +  "taskTitle": {
      +    "maxLength": 2048,
      +    "type": "string"
      +  },
      +  "webpageId": {
      +    "$ref": "#/properties/query/properties/websiteId"
      +  },
      +  "websiteId": {
      +    "anyOf": [
      +      {
      +        "exclusiveMinimum": 0,
      +        "maximum": 9007199254740991,
      +        "minimum": -9007199254740991,
      +        "type": "integer"
      +      },
      +      {
      +        "pattern": "^[1-9][0-9]{0,17}$",
      +        "type": "string"
      +      }
      +    ]
      +  },
      +  "workspaceId": {
      +    "$ref": "#/properties/query/properties/websiteId"
      +  }
      +}
  2. 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=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered structurally. The description adds genuinely useful context with the account-visibility constraint ('Returns only data visible to the linked Market Brew account'), but says nothing about result volume, default ordering, or how the paging/sorting controls affect output.

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 with the trigger front-loaded and the visibility constraint immediately after; nothing is padded. Minor redundancy in that the first sentence largely restates the tool name and title.

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?

The tool takes a fairly rich nested query object with paging, sorting, and date filters, and there is no output schema to answer what comes back. The description covers when to call it and the account-visibility boundary, but leaves an agent guessing about return shape, pagination behavior, and default sort order for a list operation.

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?

There is a single 'query' parameter whose nested properties already carry a 100% schema description coverage listing every supported filter. The description adds no filter syntax, date-format, or paging-default meaning beyond what the schema provides, so the baseline of 3 applies.

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: listing 'current Ranking Sensor tasks', and the account-scoping sentence narrows the scope further. It does not distinguish this tool from look-alike siblings such as list_top_tasks or list_task_children, so it stops short of a 5.

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?

It gives a trigger condition ('when the user asks to list current Ranking Sensor tasks'), which is more than nothing. However, it names no alternatives and gives no when-not guidance, so an agent facing a request that overlaps with list_top_tasks or list_task_children gets no routing help.

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