BriefGate

List intakes

list_intakes

Read-onlyIdempotent

List all intakes in your account, optionally filtered by status, client email, folder, or a text search.

Use this to get an overview of active projects, find a specific intake by the client's email when you have lost the intake_id, check how many intakes are currently in progress, or see what's in a folder from list_folders.

Returns { intakes: [...], total } where each intake includes intake_id, project_name, status, created_at, due_date, folder_id, and portal_url.

Input Schema

TableJSON Schema

Name	Required	Description
`q`	No	Free-text search: matches a substring of project name, client name, or client email.
`limit`	No	Maximum number of results (1–100). Default: 20.
`offset`	No	Pagination offset. Default: 0.
`status`	No	Filter by intake status. Omit to return all.
`folder_id`	No	Filter by folder, using an id from list_folders. Pass the literal string "none" to see only intakes that are not in any folder.
`client_email`	No	Filter by client email address.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`total`	Yes
`intakes`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedSep 16, 2026

removedOutput schema / additionalProperties
```
Removed value: -false
```
removedOutput schema / properties / intakes / items / additionalProperties
```
Removed value: -false
```
changedOutput schema / properties / intakes / items / properties / created_at / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
changedOutput schema / properties / intakes / items / properties / due_date / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```

changedOutput schema / properties / intakes / items / required

Previous value: -[
-  "intake_id",
-  "project_name",
-  "client_email",
-  "status",
-  "created_at",
-  "portal_url"
-]New value: +[
+  "intake_id",
+  "project_name",
+  "status",
+  "created_at",
+  "portal_url"
+]

Changed3 schema fields changedSep 16, 2026

addedInput schema / properties / folder_id

Added value: +{
+  "description": "Filter by folder, using an id from list_folders. Pass the literal string \"none\" to see only intakes that are not in any folder.",
+  "type": "string"
+}

addedInput schema / properties / q

Added value: +{
+  "description": "Free-text search: matches a substring of project name, client name, or client email.",
+  "type": "string"
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "intakes": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "client_email": {
+            "type": "string"
+          },
+          "created_at": {
+            "type": "string"
+          },
+          "due_date": {
+            "type": "string"
+          },
+          "folder_id": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "intake_id": {
+            "type": "string"
+          },
+          "portal_url": {
+            "type": "string"
+          },
+          "project_name": {
+            "type": "string"
+          },
+          "status": {
+            "enum": [
+              "draft",
+              "sent",
+              "in_progress",
+              "completed",
+              "archived"
+            ],
+            "type": "string"
+          }
+        },
+        "required": [
+          "intake_id",
+          "project_name",
+          "client_email",
+          "status",
+          "created_at",
+          "portal_url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "intakes",
+    "total"
+  ],
+  "type": "object"
+}

First observedSep 15, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already carry readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, so the description does not need to repeat those traits. It adds useful behavioral context by specifying account scope, optional filtering, and the exact response envelope with the fields included in each intake.

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?

The description is well structured and front-loaded: operation and filters first, then use cases, then return shape. The use-case sentence is slightly longer than strictly necessary, but each listed scenario earns its place by clarifying when an agent should call this tool.

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 list tool with six optional filters and zero required parameters, this description is complete: it states the operation, gives decision triggers, names the related list_folders tool, and documents the response shape. Annotations cover the safety and idempotency profile, so the agent has enough to call it correctly.

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?

The input schema has 100% parameter description coverage, including details like q substring matching, limit range, folder_id 'none' semantics, and default values. The description only summarizes the filter categories and adds no new parameter-level meaning, so the baseline of 3 is appropriate.

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?

The first sentence clearly states the operation ('List all intakes in your account') and the filter dimensions available ('status, client email, folder, or a text search'). The return-shape sentence reinforces that this is a list-level tool, distinguishing it from single-intake siblings like get_intake_status and get_intake_results.

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?

The second paragraph gives concrete use cases: overviewing active projects, finding an intake by client email when intake_id is lost, counting in-progress intakes, and inspecting a folder from list_folders. It does not explicitly tell the agent when not to use this tool or route to single-intake alternatives, but the context is clear enough to guide selection.

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

All BriefGate 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?