Summer

This connector has been deprecated

This was a duplicate manual listing. Use Summer’s official listing, imported from the official MCP Registry. Summer’s MCP server remains active at https://api.gosummer.ai/mcp. Setup and documentation: https://gosummer.ai/docs/mcp-clients.

Publish a complete release of the company's customer help center

summer_guides_publish

Destructive

Publish a complete release of the company's customer help center. The release replaces every published article: list each article that should stay public (guides.preview publication.articles) and name any published article you mean to remove in unpublish. Requires explicit publication authority; does not approve customer business actions.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "company": "<company>",
      "expected_version": "<expected_version>",
      "articles": "<articles>",
      "reason": "<reason>"
    },
    "name": "summer_guides_publish"
  }
}

Input Schema

Name	Required	Description
`reason`	Yes
`company`	Yes	Summer company ID
`articles`	Yes
`unpublish`	No
`idempotency_key`	No	Reuse the same key when retrying the same change
`expected_version`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 24, 2026

addedInput schema / properties / unpublish

Added value: +{
+  "default": [],
+  "items": {
+    "maxLength": 100,
+    "pattern": "^[a-z0-9]+(?:[.-][a-z0-9]+)*$",
+    "type": "string"
+  },
+  "maxItems": 200,
+  "type": "array"
+}

AddedOct 21, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations already declare destructiveHint=true, but the description adds crucial detail: every published article is replaced, only listed articles stay public, and removals must be named in unpublish. It also states that explicit publication authority is required and that the tool does not approve customer business actions, which is valuable behavioral and scope context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two tight sentences with no wasted language. It front-loads the destructive replacement scope before explaining the allowlist mechanics and authorization constraint.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, no-output-schema release tool, the description covers the essential replacement behavior, authority requirement, and scope boundary. It still leaves out expected_version concurrency semantics and reason guidance, so an agent could understand the high-level operation but still miss required invocation details.

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 description adds meaningful semantics for the complex articles parameter as a keep-public allowlist and for unpublish as the removal list. However, schema description coverage is only 33%, and the description leaves required expected_version and reason unexplained and does not mention that each article entry also needs a revision, leaving important gaps for a destructive call.

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 description states a specific verb and resource: publishing a complete release of the customer help center. It also distinguishes the operation from incremental edits by explaining that the release replaces every published article and that articles must be allowlisted to remain public.

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 complete-release context is clear, and the description explains the allowlist/unpublish model needed to use the tool correctly. However, it does not explicitly name when to use sibling tools such as summer_guides_unpublish or summer_guides_articles_save instead, so it falls short of full alternative routing.

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

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