Skip to main content
Glama
CiteContext MCP Server

CiteContext MCP Server

deploy_github_pr

Opens an automated GitHub pull request that deploys verified GEO remediation files—AI crawler robots.txt, /llms.txt, and Schema.org JSON-LD—to a target repository.

Instructions

Deploy verified GEO remediation files (AI crawler-unblocking robots.txt, /llms.txt, Schema.org JSON-LD) directly to a GitHub repository by opening an automated Pull Request with zero human intervention.

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": {
      "repo": "<repo>"
    },
    "name": "deploy_github_pr"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoYesTarget GitHub repository in 'owner/repo' format (e.g. 'acme/webapp')
domainNoWebsite domain name to audit and remediate (e.g. 'acme.com')
auto_mergeNoAdd zero-touch auto-merge instructions for CI/CD pipelines (default: false)
base_branchNoTarget base branch (default: 'main')main
client_slugNoOptional CiteContext workspace slug (if configured)
github_tokenNoOptional GitHub Personal Access Token (defaults to GITHUB_TOKEN env var or stored workspace PAT)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose the key behavioral trait: it opens a Pull Request rather than pushing directly, with 'zero human intervention.' It says nothing about authentication (the github_token param defaults to env/workspace PAT), rate limits, idempotency on repeated deploys, or what happens to an existing branch/PR with the same files.

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?

One front-loaded sentence with the action, payload, and mechanism in that order. No filler, no repetition of schema fields.

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 six-parameter remote-mutation tool with no annotations and no output schema, the description covers the what and the payload but omits the response (e.g. PR URL/number), auth fallback behavior, and failure semantics. An agent could invoke it but would not know what it gets back or how to recover from an error.

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 description coverage is 100%, so the baseline is 3. The description adds only indirect meaning, tying 'zero human intervention' to the auto_merge flag and implying file content originates from prior remediation work, but explains no parameter formats or precedence (e.g. token resolution order) beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb (deploy / open a Pull Request) and resource (GEO remediation files: robots.txt, /llms.txt, JSON-LD) against a GitHub repo, and the word 'verified' implicitly positions it downstream of generate_robots_txt/get_remediation_patch. It stops short of explicitly naming those siblings, so the differentiation is inferable rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Deploy verified GEO remediation files' implies this is the publishing step after files have been generated and checked, which is real guidance. There is no explicit when-not guidance, no mention of prerequisites (e.g. that the remediation artifacts must already exist), and no note on how it differs from patching locally via get_remediation_patch.

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