Google Docs tool
The docs_read tool in the developer API, with every argument: read a Google Doc as text, with headings, lists and tables.
Needs: A Google Docs connection. 1 tool, all read-only.
Google is still reviewing the permission this connector needs. Until it approves it, Plugsight offers Google Docs to Plugsight admins only, so for most people it isn't in the Connector catalog yet and these tools don't appear. See Google Docs.
These tools appear in GET /v1/tools only when the API key's MCP server includes a connection of this kind. Call each one with POST /v1/tools/\<name>, sending its arguments as a JSON object. See Calling tools for the request and response format.
Open a document by its link or id. The optional account argument takes a Google Docs connection id from list_accounts; leave it out when the MCP server has only one.
| Tool | What it does | Kind |
|---|---|---|
docs_read |
Read a Google Doc | Read |
Every tool here only reads: none of them changes anything in Google Docs, so none needs confirm.
The example requests fill in only the required arguments, with placeholder values.
docs_read
Read a Google Doc · Read
Reads a Google Docs document as text, keeping headings, bullet lists and tables (every tab of a tabbed document). Open it by its link.
| Argument | Type | Required | What it is |
|---|---|---|---|
document |
string | Yes | The document's link (from the browser's address bar) or its id |
max_chars |
integer | No | Longest text returned; longer documents are cut. From 1,000 to 500,000. Default 60000. |
account |
string | No | Google Docs connection id from list_accounts (optional when there's only one) |
Example request:
curl -X POST https://app.plugsight.app/v1/tools/docs_read \
-H "Authorization: Bearer $PLUGSIGHT_API_KEY" \
-H "Content-Type: application/json" \
-d '{"document": "…"}'