searchSearch public WeJob jobs, formations, and companies. Returns ids usable with fetch.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | One-based result page number. | |
| sort | No | Optional public result sort order. | |
| limit | No | Maximum number of results. | |
| query | Yes | Search query. |
| Name | Required | Description | Default |
|---|---|---|---|
| results | Yes | ||
| pagination | No |
Changes observed during successful MCP inspections.
Input schema / properties / sort / enumPrevious value: -[
- "newest",
- "oldest",
- "deadline_soon",
- "deadline_later",
- "price_asc",
- "price_desc",
- "smallest",
- "largest",
- "founded_newest",
- "founded_oldest",
- "most_jobs"
-]New value: +[
+ "newest",
+ "oldest",
+ "deadline_soon",
+ "deadline_later",
+ "level_asc",
+ "price_asc",
+ "price_desc",
+ "duration_asc",
+ "smallest",
+ "largest",
+ "founded_newest",
+ "founded_oldest",
+ "most_jobs"
+]Output schema / properties / results / items / properties / locationAdded value: +{
+ "type": "string"
+}Input schema / properties / pageAdded value: +{
+ "default": 1,
+ "description": "One-based result page number.",
+ "minimum": 1,
+ "type": "integer"
+}Output schema / properties / paginationAdded value: +{
+ "additionalProperties": false,
+ "properties": {
+ "has_more": {
+ "type": "boolean"
+ },
+ "limit": {
+ "type": "integer"
+ },
+ "page": {
+ "type": "integer"
+ },
+ "total": {
+ "type": "integer"
+ }
+ },
+ "required": [
+ "page",
+ "limit",
+ "has_more"
+ ],
+ "type": "object"
+}Input schema / properties / sortAdded value: +{
+ "description": "Optional public result sort order.",
+ "enum": [
+ "newest",
+ "oldest",
+ "deadline_soon",
+ "deadline_later",
+ "price_asc",
+ "price_desc",
+ "smallest",
+ "largest",
+ "founded_newest",
+ "founded_oldest",
+ "most_jobs"
+ ],
+ "type": "string"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds that results are public and return chained ids, which is helpful, but says nothing about pagination, limits, or result shape beyond the id note.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short sentences, zero waste, with the core purpose and the fetch-handoff front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return values need not be explained, yet the description supplies the key chaining detail (ids usable with fetch). The remaining gap is not clarifying its relationship to the specialized search siblings, but it is otherwise complete for correct invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so the schema already documents query, page, limit, and sort (with an enum). The description adds no parameter-level syntax or defaults, so the baseline of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb+resource: searching public WeJob jobs, formations, and companies. The scope hints it is the multi-type search versus the type-specific siblings, but the distinction is left implicit rather than stated.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Adds a useful handoff note that results are usable with fetch, implying a search-then-fetch flow. However, it gives no explicit when-to-use guidance versus the type-specific searches (wejob_search_jobs/formations/companies), so selection between them is inferred.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.