AthenaHQ

list_outreach_contacts

Read-only

Read saved Outreach contacts: cited pages with their status, author, email and where the email came from, LinkedIn, contact page, and pitch draft. Only pages someone has triaged, enriched or drafted are listed; find other cited pages with the source-page analytics tools. Newest first; use offset for the next page. Read-only.

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": {
      "website_id": "<website_id>"
    },
    "name": "list_outreach_contacts"
  }
}

Input Schema

Name	Required	Description
`url`	No	Return only this page's contact. Omit to list all.
`limit`	No	Contacts per page: 1 through 50, default 20.
`offset`	No
`statuses`	No	Only contacts in these statuses. Omit for all.
`website_id`	Yes

Output Schema

Name	Required	Description	Default
`total`	No
`contacts`	No
`has_more`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed14 schema fields changedOct 24, 2026
- removedOutput schema / properties / contacts / items / properties / assignee_email / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / contacts / items / properties / assignee_email / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / contacts / items / properties / author_name / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / contacts / items / properties / author_name / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / contacts / items / properties / contact_page_url / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / contacts / items / properties / contact_page_url / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / contacts / items / properties / email / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / contacts / items / properties / email / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / contacts / items / properties / linkedin / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / contacts / items / properties / linkedin / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / contacts / items / properties / message / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / contacts / items / properties / message / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / contacts / items / properties / subject / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / contacts / items / properties / subject / type
```
Added value: +[
+  "string",
+  "null"
+]
```
AddedOct 21, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds meaningful behavior beyond annotations: newest-first ordering, offset-based pagination, and the restriction to already-triaged/enriched/drafted pages. It repeats 'Read-only' from annotations and does not mention auth or rate limits, but the added context is substantive.

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?

Three tight sentences, front-loaded with what the tool reads and what is excluded, followed by ordering/pagination and read-only confirmation. Every sentence earns its place with no redundant 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?

An output schema exists, so return values need not be fully described; the description nonetheless enumerates returned fields helpfully. It covers filtering scope, ordering, and pagination, but does not mention the required website_id scoping, which is a minor gap for a list tool with a mandatory tenant parameter.

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 description coverage is moderate at 60%; url, limit, and statuses are documented in the schema, while offset and website_id lack schema descriptions. The description compensates by explaining that offset moves to the next page and that results are newest-first, adding ordering semantics not present in the schema. It still does not clarify the required website_id scoping, keeping it from a 5.

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 ('Read saved Outreach contacts') and enumerates exactly what is returned: status, author, email provenance, LinkedIn, contact page, and pitch draft. It also draws a clear boundary against sibling analytics tools ('find other cited pages with the source-page analytics tools'), so an agent can distinguish it from list_pitches or get_source_pages without opening schemas.

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

Usage Guidelines5/5

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

Explicitly says only pages that have been triaged, enriched, or drafted are listed, and names the alternative (source-page analytics tools) for other cited pages. It also gives pagination guidance ('Newest first; use offset for the next page'), leaving little to inference.

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

All AthenaHQ tools Inspect

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

Need Help?