Glean
Arcade MCP server exposing Glean Client API search over custom OAuth2.
0.2.0Glean Toolkit
Exposes Glean's Client API through Arcade, enabling AI agents to search an enterprise's Glean index with results scoped to the authenticated user's permissions.
Capabilities
- Enterprise search: Query the full Glean index and receive ranked, permission-filtered results tailored to the authorized user.
- Pagination: Offset-based paging via
offset+limit;has_next_pagesignals additional results. Supported up to ~2,000 results (20 pages × 100 items); deeper offsets raise an explicit error. - Budget-aware result trimming: When the fetch budget is exhausted before a requested page is filled, the tool raises an error rather than return a partial or misleading response. When items are large, the result list is trimmed and
truncatedis set whilehas_next_pageremainstrueso callers can page or narrow the query.
OAuth
This toolkit uses OAuth 2.0 with a custom/unknown provider (Glean's own OAuth layer). Refer to Glean's documentation or your Glean admin for OAuth client configuration. No Arcade-managed OAuth provider page is available for this toolkit.
Secrets
GLEAN_API_URL— The base URL for your organization's Glean Client API endpoint (e.g.,https://<your-org>.glean.com/api/v1). This value is specific to your Glean deployment. Retrieve it from your Glean admin or from the Glean admin console under Workspace Settings → API. It is not a credential but a required routing value that identifies which Glean instance to call; without it the toolkit cannot resolve requests to the correct tenant.
See the Arcade secrets guide for how to configure secrets: https://docs.arcade.dev/en/guides/create-tools/tool-basics/create-tool-secrets. You can also manage secrets directly at https://api.arcade.dev/dashboard/auth/secrets.
Available tools(1)
| Tool name | Description | Secrets | |
|---|---|---|---|
Search the user's Glean enterprise index and return ranked results.
Results are permission-filtered to the authorized user. Use 'offset' with
'limit' to page; 'has_next_page' indicates more results remain. Offset
paging is supported up to roughly 2000 results (20 pages x 100 items);
deeper offsets raise an error rather than return a misleading empty page.
When the fetch budget is exhausted before the requested window is filled,
the tool raises rather than return a partial page (fail loud over mislead).
The result list is trimmed to a size budget when items are large;
'truncated' flags it and 'has_next_page' stays true so the caller can page
or narrow the query. | 1 |
Selected tools
No tools selected.
Click "Show all tools" to add tools.
Requirements
Select tools to see requirements
Glean.Search
Execution hints
Signals for MCP clients and agents about how this tool behaves.
Reads data without modifying any state in the target system.
May permanently delete or overwrite data in the target system.
Repeated calls with the same inputs produce no additional effect.
Communicates with external APIs, databases, or other services.
Search the user's Glean enterprise index and return ranked results. Results are permission-filtered to the authorized user. Use 'offset' with 'limit' to page; 'has_next_page' indicates more results remain. Offset paging is supported up to roughly 2000 results (20 pages x 100 items); deeper offsets raise an error rather than return a misleading empty page. When the fetch budget is exhausted before the requested window is filled, the tool raises rather than return a partial page (fail loud over mislead). The result list is trimmed to a size budget when items are large; 'truncated' flags it and 'has_next_page' stays true so the caller can page or narrow the query.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
query | string | Required | Natural-language search query to run against the user's Glean index. |
limit | integer | Optional | Maximum number of results to return (1-100). Defaults to 10. |
offset | integer | Optional | 0-indexed position of the first result to return. Defaults to 0 (first result). |
Requirements
Output
json— Ranked Glean results plus pagination metadata. 'has_next_page' is true when more results are available (page with a larger 'offset'); 'truncated' is true when the result list was trimmed to fit a response-size budget.