Skip to main content
Glama

search_campus_jobs

Read-only

Search open roles on AceRound's job board and return the first page of results, one role per line. Apply links and further pages require signing in on the website.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_campus_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoWork location, from the city line of get_campus_job_filters
sortNohot = most popular, recent = most recently found, published = most recently postedhot
companyNoCompany name
keywordNoKeyword in the job title or description, such as "backend" or "product manager"
jobFunctionNoJob function, one of the jobFunction values from get_campus_job_filters
employmentTypeNoEmployment type, one of the employmentType values from get_campus_job_filters

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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 genuinely non-obvious behavior: results are limited to the first page and rendered one role per line, and deeper paging/apply requires sign-in on the website. Those are constraints an agent cannot infer from the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the action and scope, followed by the one limitation that changes agent behavior. No restatement of the name and no filler.

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?

For a six-parameter, all-optional read tool with no output schema, the description covers purpose, result shape, and the hard pagination/auth limit. It leaves minor gaps (empty-result behavior, maximum result count per page) but nothing that would cause a misinvocation.

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 per-parameter explanations and an enum for sort, so the schema carries the semantics. The description adds nothing about filtering behavior (e.g., whether filters combine as AND, or what happens with zero filters), so this sits at the baseline.

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?

States a specific verb and resource ("Search open roles on AceRound's job board") plus the return scope ("first page of results, one role per line"). It is not confused with the apply-list or filter siblings, though it never names an alternative explicitly.

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 product context — you call this to find roles, then act on them elsewhere. The description does add a boundary condition (pages beyond the first and apply links require website sign-in), but it gives no explicit when-to-use vs. when-not guidance relative to siblings like get_campus_job_filters.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources