Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

jobs_pinpoint_board

List a tenant's Pinpoint job board postings and return inline details including full HTML descriptions, responsibilities, skills, benefits, and structured pay ranges.

Instructions

List a tenant's Pinpoint job board. Lists a tenant's public Pinpoint (pinpointhq.com) board postings with inline detail (full HTML description, key responsibilities, skills, and benefits, plus structured compensation when the tenant publishes a pay range). The company is the tenant subdomain from its careers URL https://{company}.pinpointhq.com/.

Input Schema

NameRequiredDescriptionDefault
companyYesPinpoint tenant subdomain (careers URL)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden, and it does disclose meaningful behavior: the board is public, results include inline detail (HTML description, responsibilities, skills, benefits) and structured compensation only when the tenant publishes a pay range. It omits rate limits, pagination, and auth requirements, but for a read-only list tool this is solid disclosure.

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?

Front-loaded with the core action, then scoped detail, then the parameter explanation. There is mild redundancy between 'List a tenant's Pinpoint job board' and 'Lists a tenant's public Pinpoint board postings', but overall it is tight and well-ordered.

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?

With no output schema or annotations, the description compensates by describing the returned content in detail, so an agent knows what it gets. For a single-parameter read tool this is nearly complete, with only pagination/volume expectations left unstated.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds value beyond the schema by spelling out the exact value format: the company is the tenant subdomain from the careers URL https://{company}.pinpointhq.com/. That removes ambiguity about what string to supply.

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?

States a specific verb (List) and resource (Pinpoint job board postings) and elaborates the payload (full HTML description, responsibilities, skills, benefits, compensation). The explicit 'Pinpoint (pinpointhq.com)' qualifier distinguishes it from the many other ATS board siblings like jobs_greenhouse_board and jobs_lever_postings.

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?

Usage is implied by the Pinpoint-specific naming and URL format, so an agent can infer it applies to Pinpoint-hosted career sites rather than other ATS platforms. However, it never explicitly states when to choose this over sibling board tools or any prerequisites, leaving routing to inference.

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