Skip to main content
Glama
Sign In

Joeb

by com.joebapp
OverviewDiscussionsAdmin

Unblock companies

unblock_companies
DestructiveIdempotent

Unblock companies the user has blocked, so search includes their postings again.

Takes 1 to 25 block ids: the number in a list_blocked_companies line's [block {id}], not a job id. A block id named twice counts once.

All or nothing: every id is checked to be one of the user's blocks before anything is unblocked. If any is not, nothing is unblocked and the error names each such id.

Returns the companies unblocked. Their postings come back into search_jobs, except the jobs the user already liked, dismissed or applied to, which search always leaves out.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "block_ids": "<block_ids>"
    },
    "name": "unblock_companies"
  }
}

Input Schema

NameRequiredDescriptionDefault
block_idsYesThe blocks to lift, 1 to 25: each the number in a list_blocked_companies line's [block {id}].

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, but the description adds genuinely new behavior: all-or-nothing validation, duplicate ids counting once, and an error that names every invalid id. It also discloses the return value and the search-side side effect, going well beyond the annotation set.

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?

Short paragraphs with the payoff stated first and constraints following. Every sentence carries information; the line-broken formatting is slightly fragmented but never padded.

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 one-parameter mutation with no output schema, the description covers validation rules, error shape, return value, and post-condition on search. There is nothing an agent needs in order to call it correctly that is missing.

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% and the schema already states the 1-25 range and where the id comes from. The description still adds real meaning by warning that this is a block id and not a job id, which is the most likely caller mistake here.

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 and resource ('Unblock companies the user has blocked') plus the effect ('so search includes their postings again'). It is trivially distinguishable from siblings block_companies and list_blocked_companies, which the text implicitly positions around it.

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

Usage Guidelines4/5

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

It routes the agent to list_blocked_companies as the source of valid ids and explains the downstream condition (postings return to search_jobs except already-liked/dismissed/applied jobs). It never states an explicit 'do not use when' case, which keeps it below a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Joeb toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources