mcp-google-sheets

{ "Integration key / Client ID": "Integration key / Client ID", "RSA private key": "RSA private key", "Environment": "Environment", "Impersonated user ID": "Impersonated user ID", "scopes": "scopes", "This can be obtained in your developer account from the<https://admindemo.docusign.com/authenticate?goTo=appsAndKeys|Apps and Keys> page. See the https://support.docusign.com/guides/ndse-admin-guide-api-and-keys|Docusign eSignature Admin Guide> for more information.": "This can be obtained in your developer account from the<https://admindemo.docusign.com/authenticate?goTo=appsAndKeys|Apps and Keys> page. See the https://support.docusign.com/guides/ndse-admin-guide-api-and-keys|Docusign eSignature Admin Guide> for more information.", "This is for the integration key you obtained above and can also be created on the <https://admindemo.docusign.com/authenticate?goTo=appsAndKeys|Apps and Keys> page. You only need the private key, and it can only be copied once. Make sure to retain it for your records.": "This is for the integration key you obtained above and can also be created on the <https://admindemo.docusign.com/authenticate?goTo=appsAndKeys|Apps and Keys> page. You only need the private key, and it can only be copied once. Make sure to retain it for your records.", "This is a GUID identifying the Docusign user that you will be impersonating with the access token. Your own User ID can be found at the top of the<https://admindemo.docusign.com/authenticate?goTo=appsAndKeys|Apps and Keys> page": "This is a GUID identifying the Docusign user that you will be impersonating with the access token. Your own User ID can be found at the top of the<https://admindemo.docusign.com/authenticate?goTo=appsAndKeys|Apps and Keys> page", "Comma-separated list of scopes. These represent the OAuth scopes (permissions) that are being requested. For eSignature REST API methods, use the signature scope. The impersonation scope is implied by the JWT Grant operation and does not need to be included. If the access token will be used for other Docusign APIs, additional scopes may be required; see each API’s <https://developers.docusign.com/docs/esign-rest-api/esign101/auth/|authentication> requirements": "Comma-separated list of scopes. These represent the OAuth scopes (permissions) that are being requested. For eSignature REST API methods, use the signature scope. The impersonation scope is implied by the JWT Grant operation and does not need to be included. If the access token will be used for other Docusign APIs, additional scopes may be required; see each API’s <https://developers.docusign.com/docs/esign-rest-api/esign101/auth/|authentication> requirements", "Demo / Test": "Demo / Test", "US production": "US production", "EU production": "EU production", "List envelopes": "List envelopes", "Get envelope": "Get envelope", "Get document": "Get document", "Custom API Call": "Custom API Call", "List / search envelopes": "List / search envelopes", "Get Docusign envelope": "Get Docusign envelope", "Get document from a specific envelope": "Get document from a specific envelope", "Make a custom API call to a specific endpoint": "Make a custom API call to a specific endpoint", "Account ID": "Account ID", "From date": "From date", "To date": "To date", "Search text": "Search text", "Status": "Status", "Include (e.g. recipients)": "Include (e.g. recipients)", "Envelope ID": "Envelope ID", "Document ID": "Document ID", "Method": "Method", "Headers": "Headers", "Query Parameters": "Query Parameters", "Body": "Body", "Response is Binary ?": "Response is Binary ?", "No Error on Failure": "No Error on Failure", "Timeout (in seconds)": "Timeout (in seconds)", "The ID of the document to retrieve. Alternatively, you can use one of the following special keywords:\n\ncombined: Retrieves all of the documents as a single PDF file. When the query parameter certificate is true, the certificate of completion is included in the PDF file. When the query parameter certificate is false, the certificate of completion is not included in the PDF file.\narchive: Retrieves a ZIP archive that contains all of the PDF documents and the certificate of completion.\ncertificate: Retrieves o": "The ID of the document to retrieve. Alternatively, you can use one of the following special keywords:\n\ncombined: Retrieves all of the documents as a single PDF file. When the query parameter certificate is true, the certificate of completion is included in the PDF file. When the query parameter certificate is false, the certificate of completion is not included in the PDF file.\narchive: Retrieves a ZIP archive that contains all of the PDF documents and the certificate of completion.\ncertificate: Retrieves only the certificate of completion as a PDF file.\nportfolio: Retrieves the envelope documents as a PDF portfolio.\n", "Authorization headers are injected automatically from your connection.": "Authorization headers are injected automatically from your connection.", "Enable for files like PDFs, images, etc..": "Enable for files like PDFs, images, etc..", "GET": "GET", "POST": "POST", "PATCH": "PATCH", "PUT": "PUT", "DELETE": "DELETE", "HEAD": "HEAD" }