Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

upwork_search

Search Upwork's public job listings by keyword, returning concise summaries with title, budget, experience level, duration, posted date, description snippet, and skill tags.

Instructions

Search Upwork job postings. Searches Upwork's public job listings by free-text keyword, returning job summaries (title, budget, experience level, duration, posted date, description snippet, skill tags).

Input Schema

NameRequiredDescriptionDefault
qYesFree-text job search keyword
pageNo1-based result page. Defaults to 1.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully enumerates the returned summary fields (title, budget, experience level, duration, posted date, snippet, skills), but says nothing about read-only safety, rate limits, result counts per page, or how fresh the postings are.

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 compact sentences, front-loaded with the core action. The opening "Search Upwork job postings" is slightly redundant with the following sentence, but the second sentence earns its place by adding the scope and the returned fields.

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

Completeness3/5

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

With no annotations and no output schema, the description does compensate somewhat by listing the returned job-summary fields, which is the most valuable missing structured data. However, it omits pagination scale and any indication that this is a safe read-only public search, leaving gaps for a zero-annotation tool.

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%, with both q and page fully documented in the schema, so the baseline is 3. The description repeats the free-text keyword concept without adding syntax, matching behavior, or paging semantics beyond what the schema already states.

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 gives a specific verb and resource (search Upwork job postings) and scopes it to "Upwork's public job listings" searched by free-text keyword. It is clear what the tool returns, though it never explicitly contrasts with the sibling upwork_job detail tool, so sibling differentiation is left to inference.

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

Usage Guidelines2/5

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

There is no guidance on when to use this search versus fetching an individual job (upwork_job) or freelancer profiles, and no stated prerequisites, limits, or exclusions. The description only says what it does, not when it is the right choice.

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