Skip to main content
Glama

List outreach requests

listOutreachRequests
Read-onlyIdempotent

List the outreach your company has asked Clera to run with requestOutreach, newest first, with where each one stands: being prepared, live, or failed.

Clera privately records this tool's inputs and results for usage tracking and support.

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": "listOutreachRequests"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgIdNoOrganization to act as. Only needed when you belong to more than one organization.

Output Schema

NameRequiredDescriptionDefault
requestsYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), so the remaining burden is light. The description still adds real behavior beyond them: newest-first ordering, the enumerated lifecycle states, and a data-retention disclosure that the tool's inputs and results are recorded for usage tracking and support.

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 sentences, front-loaded with what is listed, the ordering, and the status set before the secondary privacy note. Nothing is redundant, though the logging sentence reads as boilerplate that could sit in a footer rather than the core description.

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?

A low-complexity, zero-required-parameter read tool with an output schema present, so return shape need not be described. Ordering, state vocabulary, and provenance are all covered; the only mild gap is that no result limit or pagination behavior is mentioned for a list operation.

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?

Only one optional parameter (orgId) exists and schema description coverage is 100%, so the schema fully documents that membership in multiple orgs is what triggers it. The description adds nothing about the parameter, leaving this at the baseline for high-coverage schemas.

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 ('List the outreach your company has asked Clera to run with requestOutreach') and immediately scopes it to outreach requests produced by a named sibling, which separates it from look-alikes such as listInterviewRequests or listPendingIntroRequests.

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?

Makes the usage context explicit by tying the listing to requestOutreach output and describing the states returned (being prepared, live, failed), so an agent knows this is the status-tracking read. It stops short of stating when NOT to use it or naming the alternative to pick for a different request type.

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