Skip to main content
Glama

Market Brew

List child tasks

list_task_children
Read-onlyIdempotent

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

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "taskId": "<taskId>"
    },
    "name": "list_task_children"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed18 schema fields changed
    • removedInput schema / properties / query / properties / boostFactorId / $ref
      Removed value: -"#/properties/taskId"
    • addedInput schema / properties / query / properties / boostFactorId / anyOf
      Added value: +[
      +  {
      +    "exclusiveMinimum": 0,
      +    "maximum": 9007199254740991,
      +    "type": "integer"
      +  },
      +  {
      +    "pattern": "^[1-9][0-9]{0,17}$",
      +    "type": "string"
      +  }
      +]
    • 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"
    • removedInput schema / properties / query / properties / rankingSensorId / $ref
      Removed value: -"#/properties/taskId"
    • addedInput schema / properties / query / properties / rankingSensorId / anyOf
      Added value: +[
      +  {
      +    "exclusiveMinimum": 0,
      +    "maximum": 9007199254740991,
      +    "type": "integer"
      +  },
      +  {
      +    "pattern": "^[1-9][0-9]{0,17}$",
      +    "type": "string"
      +  }
      +]
    • removedInput schema / properties / query / properties / snapshotId / $ref
      Removed value: -"#/properties/taskId"
    • addedInput schema / properties / query / properties / snapshotId / anyOf
      Added value: +[
      +  {
      +    "exclusiveMinimum": 0,
      +    "maximum": 9007199254740991,
      +    "type": "integer"
      +  },
      +  {
      +    "pattern": "^[1-9][0-9]{0,17}$",
      +    "type": "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])))$"
    • removedInput schema / properties / query / properties / webpageId / $ref
      Removed value: -"#/properties/taskId"
    • addedInput schema / properties / query / properties / webpageId / anyOf
      Added value: +[
      +  {
      +    "exclusiveMinimum": 0,
      +    "maximum": 9007199254740991,
      +    "type": "integer"
      +  },
      +  {
      +    "pattern": "^[1-9][0-9]{0,17}$",
      +    "type": "string"
      +  }
      +]
    • removedInput schema / properties / query / properties / websiteId / $ref
      Removed value: -"#/properties/taskId"
    • addedInput schema / properties / query / properties / websiteId / anyOf
      Added value: +[
      +  {
      +    "exclusiveMinimum": 0,
      +    "maximum": 9007199254740991,
      +    "type": "integer"
      +  },
      +  {
      +    "pattern": "^[1-9][0-9]{0,17}$",
      +    "type": "string"
      +  }
      +]
    • removedInput schema / properties / query / properties / workspaceId / $ref
      Removed value: -"#/properties/taskId"
    • addedInput schema / properties / query / properties / workspaceId / anyOf
      Added value: +[
      +  {
      +    "exclusiveMinimum": 0,
      +    "maximum": 9007199254740991,
      +    "type": "integer"
      +  },
      +  {
      +    "pattern": "^[1-9][0-9]{0,17}$",
      +    "type": "string"
      +  }
      +]
    • changedInput schema / properties / taskId / 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
    • addedInput schema / properties / query / properties
      Added value: +{
      +  "boostFactorId": {
      +    "$ref": "#/properties/taskId"
      +  },
      +  "endDate": {
      +    "$ref": "#/properties/query/properties/startDate"
      +  },
      +  "offset": {
      +    "maximum": 1000000,
      +    "minimum": 0,
      +    "type": "integer"
      +  },
      +  "pageSize": {
      +    "maximum": 200,
      +    "minimum": 1,
      +    "type": "integer"
      +  },
      +  "rankingSensorId": {
      +    "$ref": "#/properties/taskId"
      +  },
      +  "serverHost": {
      +    "maxLength": 253,
      +    "type": "string"
      +  },
      +  "snapshotId": {
      +    "$ref": "#/properties/taskId"
      +  },
      +  "sortBy": {
      +    "maxLength": 80,
      +    "type": "string"
      +  },
      +  "sortDir": {
      +    "enum": [
      +      "asc",
      +      "desc"
      +    ],
      +    "type": "string"
      +  },
      +  "startDate": {
      +    "format": "date",
      +    "type": "string"
      +  },
      +  "taskTitle": {
      +    "maxLength": 2048,
      +    "type": "string"
      +  },
      +  "webpageId": {
      +    "$ref": "#/properties/taskId"
      +  },
      +  "websiteId": {
      +    "$ref": "#/properties/taskId"
      +  },
      +  "workspaceId": {
      +    "$ref": "#/properties/taskId"
      +  }
      +}
    • changedInput schema / properties / taskId / anyOf
      Previous value: -[
      -  {
      -    "minLength": 1,
      -    "type": "string"
      -  },
      -  {
      -    "type": "number"
      -  }
      -]New value: +[
      +  {
      +    "exclusiveMinimum": 0,
      +    "maximum": 9007199254740991,
      +    "minimum": -9007199254740991,
      +    "type": "integer"
      +  },
      +  {
      +    "pattern": "^[1-9][0-9]{0,17}$",
      +    "type": "string"
      +  }
      +]
  3. First observed

TDQS

B3.3/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 adds genuine context by stating results are scoped to what the linked Market Brew account can see, but it omits whether only direct children are returned or the whole subtree, and says nothing about pagination defaults despite a nested query object with pageSize and offset.

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 usage trigger front-loaded and no redundant filler. The second sentence about the Market Brew account is terse to the point of being slightly cryptic, but it earns its place by conveying a visibility constraint.

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-required-parameter listing tool with rich annotations and no output schema, the definition covers trigger, scope and visibility. The remaining gaps — pagination behavior, recursion depth, and what taskId represents — are real but moderate against the tool's low complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%; the nested query object carries its own filter enumeration, but the required taskId has no description anywhere, and the description adds no meaning about what it identifies or what format it accepts. With half the parameters undocumented and the description silent on all of them, it does not compensate for the coverage gap.

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 names a specific verb and resource (list child tasks) and the required taskId in the schema anchors it as a per-parent listing, which distinguishes it reasonably from list_tasks and get_task. It never explicitly contrasts itself with those siblings, so the differentiation is implied rather than stated.

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?

'Use this when the user asks to list child tasks' gives a triggering condition but nothing about when to prefer list_tasks, get_task, or list_task_history instead. Usage is implied by the phrase rather than reasoned about, leaving the agent to infer the boundary between the flat task list and the hierarchical one.

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