Refine Job Search

inbox.get_thread

Read-onlyIdempotent

Fetch the full email thread for an inbox item

Input Schema

Name	Required	Description	Default
`item_id`	Yes	Inbox item id

Output Schema

Name	Required	Description	Default
`data`	Yes
`meta`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed14 schema fields changedOct 22, 2026
- removedOutput schema / properties / data / items / properties / body / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / data / items / properties / body / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / data / items / properties / from / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / data / items / properties / from / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / data / items / properties / id / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  }
-]
```
- addedOutput schema / properties / data / items / properties / id / type
```
Added value: +[
+  "string",
+  "number"
+]
```
- removedOutput schema / properties / data / items / properties / preview / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / data / items / properties / preview / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / data / items / properties / sent_at / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / data / items / properties / sent_at / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / meta / properties / next_page / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / meta / properties / next_page / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / meta / properties / total_count / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / meta / properties / total_count / type
```
Added value: +[
+  "number",
+  "null"
+]
```
AddedAug 23, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered without description help. The description's use of 'full' adds a small hint that the whole thread rather than a truncated view is returned, but nothing is said about whether reading marks the item read, pagination, or attachment handling.

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?

One sentence, front-loaded with the verb and resource, zero wasted words. Nothing padded or repeated from the schema.

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?

With rich annotations, a 100% documented single parameter, and an output schema covering return values, the description is close to sufficient. The remaining gap is the lack of explicit contrast with inbox.get for an agent choosing between them.

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 coverage is 100% with a single required parameter documented as 'Inbox item id', so the schema carries the semantics. The description only restates 'for an inbox item' and adds no format, sourcing, or ID-resolution detail beyond that.

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 ('Fetch') and resource ('full email thread') scoped to 'an inbox item', which is clearly distinct from siblings like inbox.get or inbox.list. It stops short of explicitly contrasting itself with inbox.get, which fetches a single item, so the differentiation from that closest sibling is only inferable.

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 only implied: the word 'full' hints that this is the right tool when the complete conversation is needed rather than the single item returned by inbox.get, but no when-to-use condition or alternative is named. An agent must infer the routing decision from sibling names alone.

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

All Refine Job Search tools Inspect

Try in Browser

Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?