Skip to main content
Glama
chrischall

jobber-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Read a Client Hub page as text

jobber_read_page
Read-onlyIdempotent

Fetch readable text from Jobber Client Hub pages for appointments, invoices, quotes, and work requests, with optional ID. Use when list tools return no results or to inspect unpinned layouts.

Instructions

Fetch a read page of a Jobber Client Hub — appointments, invoices, quotes or work_requests, optionally with a numeric id — and return its readable text. Use for detail pages (e.g. invoices/150208512, appointments/2236612358) whose layout has no pinned schema, and to inspect a page when a list tool returns nothing. Other hub routes (logout, forms, payment pages) are refused. Read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hubNoWhich provider hub to read, by label. Omit when only one is configured.
pathYesHub-relative read path: "appointments", "invoices", "quotes" or "work_requests", optionally with a numeric id, e.g. "invoices/150208512".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.0.2
    • changedInput schema / properties / path / description
      Previous value: -"Hub-relative path, e.g. \"invoices\" or \"invoices/150208512\"."New value: +"Hub-relative read path: \"appointments\", \"invoices\", \"quotes\" or \"work_requests\", optionally with a numeric id, e.g. \"invoices/150208512\"."
    • changedInput schema / properties / path / pattern
      Previous value: -"^[A-Za-z0-9_\\-/.?=&]+$"New value: +"^\\/?(?:appointments|invoices|quotes|work_requests)(?:\\/\\d+)?(?:\\?[A-Za-z0-9_]+=[A-Za-z0-9_-]*(?:&[A-Za-z0-9_]+=[A-Za-z0-9_-]*)*)?$"
  2. Changed1 schema field changedv0.4.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. First observedv0.0.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the bar is lower. The description adds value beyond them by disclosing that certain hub routes are refused, and by stating the return format is 'readable text'. No contradiction with the read-only semantics.

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?

Three focused sentences: purpose, usage guidance, and exclusions/refusals. The core purpose is front-loaded, examples are illustrative rather than filler, and every sentence earns its place.

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

Completeness5/5

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

For a moderately complex read tool with no output schema, the description plus rich schema covers: valid paths (pattern + examples), return format ('readable text'), when to use it, and route exclusions. Annotations cover safety. Minor gaps like error behavior for nonexistent ids exist, but everything an agent needs to call the tool correctly is present.

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 the baseline is 3. The path parameter's schema already documents the allowed routes, the numeric-id option, and the pattern; the description's example paths ('invoices/150208512') reinforce but don't add meaning beyond the schema. The optional hub parameter is covered by its own schema description.

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 opens with a specific verb ('Fetch') and resource ('read page of a Jobber Client Hub'), then scopes the resource to four concrete route types with examples. It clearly differentiates from the sibling list tools by framing this as the detail-page reader for pages 'whose layout has no pinned schema'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-to-use guidance is given: detail pages with no pinned schema, and inspecting a page 'when a list tool returns nothing'. When-not-to-use is also explicit: 'Other hub routes (logout, forms, payment pages) are refused.' The alternative (list tools) is referenced directly.

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