Skip to main content
Glama
debanjanbasu

grr

by debanjanbasu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

gmail.users.settings.sendAs.smimeInfo.insert

Uploads an S/MIME certificate configuration for a Gmail send-as alias, requiring a PKCS#12 key, so the alias can sign or encrypt mail.

Instructions

Insert (upload) the given S/MIME config for the specified send-as alias. Note that pkcs12 format is required for the key. For more information, see Manage S/MIME certificates with the Gmail API [HTTP POST] — creates or triggers a change; refused under --readonly safety profiles. Returns the API's response resource as JSON — request body is a JSON SmimeInfo object accepting encryptedKeyPassword, expiration, id, isDefault, issuerCn, pem, pkcs12; pass it via params or whole via body_file Siblings over the same resource: delete, get, list, setDefault.

Input Schema

NameRequiredDescriptionDefault
queryNoExtra KEY=VALUE query pairs for endpoints whose parameters Discovery does not describe.
paramsNoParameter map merged into the request; typed parameters win.
userIdYes[URL path segment] The user's email address. The special value `me` can be used to indicate the authenticated user.me
dry_runNoReturn the request that would be sent, without sending it.
body_fileNoRead the request body from this file ('-' for stdin) instead of building one from the parameters. The body is a JSON SmimeInfo object.
sendAsEmailYes[URL path segment] The email address that appears in the "From:" header for mail sent using this alias.
request_bodyNoRequest body of type SmimeInfo: pass it via `params` (merged into the built body) or whole via `body_file`.

Output Schema

NameRequiredDescriptionDefault
idNo
pemNo
pkcs12No
issuerCnNo
isDefaultNo
expirationNo
encryptedKeyPasswordNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / body_file / description
      Previous value: -"Read the request body from this file ('-' for stdin) instead of building one from the parameters."New value: +"Read the request body from this file ('-' for stdin) instead of building one from the parameters. The body is a JSON SmimeInfo object."
    • addedInput schema / properties / request_body
      Added value: +{
+  "description": "Request body of type SmimeInfo: pass it via `params` (merged into the built body) or whole via `body_file`.",
+  "properties": {
+    "encryptedKeyPassword": {
+      "type": "string"
+    },
+    "expiration": {
+      "type": "string"
+    },
+    "id": {
+      "type": "string"
+    },
+    "isDefault": {
+      "type": "boolean"
+    },
+    "issuerCn": {
+      "type": "string"
+    },
+    "pem": {
+      "type": "string"
+    },
+    "pkcs12": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. Changed4 schema fields changed
    • changedInput schema / properties / sendAsEmail / description
      Previous value: -"The email address that appears in the \"From:\" header for mail sent using this alias."New value: +"[URL path segment] The email address that appears in the \"From:\" header for mail sent using this alias."
    • addedInput schema / properties / userId / default
      Added value: +"me"
    • changedInput schema / properties / userId / description
      Previous value: -"The user's email address. The special value `me` can be used to indicate the authenticated user."New value: +"[URL path segment] The user's email address. The special value `me` can be used to indicate the authenticated user."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "encryptedKeyPassword": {
+      "type": "string"
+    },
+    "expiration": {
+      "type": "string"
+    },
+    "id": {
+      "type": "string"
+    },
+    "isDefault": {
+      "type": "boolean"
+    },
+    "issuerCn": {
+      "type": "string"
+    },
+    "pem": {
+      "type": "string"
+    },
+    "pkcs12": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  3. First observed

TDQS

A4.1/5.0
Behavior4/5

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

No annotations are provided, so the description carries the burden and does substantial work: it flags an actual mutation ('creates or triggers a change'), states it is refused under --readonly safety profiles, and notes the pkcs12 key requirement. It omits required auth scopes and whether an existing certificate is replaced, which keeps it out of 5 territory.

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?

Purpose is front-loaded in the first sentence and the constraints follow immediately; the doc link and sibling enumeration are appended compactly. The single run-on block mixing HTTP method, safety-profile note, body fields and siblings is dense but not wasteful.

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 an output schema present, the brief return-value note suffices, and the body format, key constraint, and mutating nature are all covered. Missing: prerequisites that the send-as alias must already exist and be verified, which matters for a nested settings resource.

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%, so the schema already documents userId, sendAsEmail, params, body_file and the encoded body fields. The description restates the SmimeInfo field list and the params/body_file routing that the schema already declares, adding little beyond the baseline.

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 states a specific verb (Insert/upload), a specific resource (S/MIME config), and its scope (the given send-as alias). An agent can distinguish this from setDefault or list without consulting the schema.

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?

Naming the sibling operations over the same resource (delete, get, list, setDefault) situates this as the create operation, and the pkcs12-required note is an actionable precondition. It stops short of explicitly saying when to pick this over patching an existing alias config, so no full 5.

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

Deploy Server

Other Tools