Skip to main content
Glama
Sign In
phabricator-mcp

phabricator-mcp

by freelancer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

phabricator_build_log_search

Read-only

Search Harbormaster build logs by build target PHID, log ID, or log PHID to inspect build step output. Find target PHIDs first with the build target search tool.

Instructions

Search Harbormaster build logs (output from build steps). Use phabricator_build_target_search to find target PHIDs first.

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": "phabricator_build_log_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNoCursor for next-page pagination
limitNoMaximum results (max 100)
orderNoResult order
beforeNoCursor for previous-page pagination
queryKeyNoBuilt-in query: "all"
constraintsNoSearch constraints

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.19

TDQS

A3.8/5.0
Behavior3/5

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

readOnlyHint=true already declares this is a safe read, so the bar is lower. The description adds that results are log output from build steps, but says nothing about volume, whether full log text is returned or truncated, or pagination expectations beyond what the schema's cursor params already imply.

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?

Two sentences, zero filler; the resource identification leads and the prerequisite hint follows. Nothing could be removed without losing information.

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?

No output schema exists, but the parenthetical 'output from build steps' tells the agent what the returned entities are, and all parameters are optional with full schema docs. Only the shape/truncation of log content is left unstated.

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 all six parameters including the nested constraints object are documented in structured form. The description only indirectly touches buildTargetPHIDs via the prerequisite hint and adds no format or semantics beyond the schema, so the baseline 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?

States a specific verb ('Search') and resource ('Harbormaster build logs') and adds a clarifier that these are build-step output, which separates them from build records or build targets. It does not explicitly contrast with phabricator_build_search, the nearest sibling, so it falls just short of full sibling differentiation.

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?

Gives a concrete prerequisite: use phabricator_build_target_search to resolve target PHIDs before calling this. That is real routing guidance an agent can act on, though there are no when-not conditions or notes on when a bare queryKey='all' call is appropriate.

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