Skip to main content
Glama
Sign In
zillow-leads-property-data

zillow-leads-property-data

by kmatata
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

get-actor-run-log

Retrieve recent log lines for an Actor run to track live collection progress or review the tail of a failed run. Provide the run ID and optionally adjust the number of lines to get the full log.

Instructions

Retrieve recent log lines for a specific Actor run — live collection progress, or the tail of a FAILED run.

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": {
      "runId": "<runId>"
    },
    "name": "get-actor-run-log"
  }
}

Input Schema

NameRequiredDescriptionDefault
linesNoOutput the last NUM lines, instead of the last 10. Pass 0 to return the entire log.
runIdYesThe ID of the Actor run.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.9

TDQS

A4/5.0
Behavior3/5

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

Without annotations, the description carries the full behavioral burden. It states what the tool retrieves and hints at the type of run states (live vs failed), but it does not disclose behavior like whether logs are truncated, how pagination works, or any side effects. It is functional but minimal.

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?

The description is a single, front-loaded sentence that conveys the core function and the key usage context. Every part adds value, and there is no repetition of schema details.

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 two-parameter read tool with complete schema coverage, the description provides enough context to choose and invoke it correctly. A bit more detail about the return format or when to prefer sibling tools would be helpful, but this is adequate.

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%, so both parameters are already documented. The description adds no additional meaning to the parameters; it merely frames the tool's purpose.

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?

The description names a specific verb ('Retrieve'), a specific resource ('recent log lines for a specific Actor run'), and clarifies its intended use for live progress or debugging failed runs. This clearly distinguishes it from siblings like get-actor-run.

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?

The description communicates when the tool is useful: to inspect live collection progress or diagnose a failed run. It does not explicitly exclude alternatives or name a sibling to use instead, but the context is clear enough for an agent to match its intent to this tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools