searchSearch public WeJob jobs, formations, and companies. Returns ids usable with fetch.
| Name | Required | Description | Default |
|---|---|---|---|
| sort | No | Optional public result sort order. | |
| limit | No | Maximum number of results. | |
| query | Yes | Search query. |
| Name | Required | Description | Default |
|---|---|---|---|
| results | Yes |
Changes observed during successful MCP inspections.
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. The description adds value by stating it returns IDs usable with fetch and that it searches public results. This provides behavioral context beyond annotations, though pagination or rate limits are not mentioned.
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?
One single sentence that conveys purpose and result format with zero waste. Front-loaded and efficient.
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?
Given the tool has 3 parameters, output schema, and annotations, the description is complete enough. It specifies the search scope and return format, though it could hint at the combined nature of results (mixing types) for extra clarity.
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 baseline 3 applies. The description adds no specific details on parameters beyond what the schema provides (e.g., query, sort, limit are already described in the schema).
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?
The description clearly states it searches public WeJob jobs, formations, and companies, and distinguishes itself from specific sibling tools like wejob_search_jobs by being a unified search. The verb 'search' and resources are specific.
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?
The description implies usage for combined searches across jobs, formations, and companies, but it does not explicitly state when to use this general search over the specific siblings (e.g., for broader queries) or when not to use it.
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.