Skip to main content
Glama

Create GitHub Issue with Journal Entry

create_github_issue_with_entry

Creates a GitHub issue and automatically adds a linked journal entry to document the issue creation.

Instructions

Create a GitHub issue AND automatically create a linked journal entry documenting the issue creation.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_github_issue_with_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNoIssue body/description
repoNoRepository name - LEAVE EMPTY to auto-detect
tagsNoJournal entry tags
ownerNoRepository owner - LEAVE EMPTY to auto-detect
titleNoIssue title
labelsNoLabels to apply
assigneesNoUsers to assign
use_test_dbNo
entry_contentNoCustom journal content (defaults to auto-generated summary)
initial_statusNoInitial status column (e.g., "Backlog", "Ready"). Defaults to "Backlog" when adding to a project.
project_numberNoGitHub Project number to add this issue to
milestone_numberNoMilestone number to assign this issue to

Output Schema

NameRequiredDescriptionDefault
codeNoError code (e.g. VALIDATION_ERROR, INTERNAL_ERROR)
errorNoHuman-readable error message
issueNo
detailsNoAdditional error context
messageNo
projectNo
successNo
categoryNoError category (validation, query, connection, internal)
suggestionNoSuggested fix for the error
instructionNo
recoverableNoWhether the error is recoverable
journalEntryNo
aggregated_errorsNoDetails of individual errors in a multi-step operation
requiresUserInputNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv9.1.0
    • changedInput schema / properties / milestone_number / type
      Previous value: -"number"New value: +[
      +  "number",
      +  "string"
      +]
    • changedInput schema / properties / project_number / type
      Previous value: -"number"New value: +[
      +  "number",
      +  "string"
      +]
  2. First observedv9.0.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-idempotent, open-world operation, so the safety profile is carried by structured data. The description usefully discloses the hidden side effect of creating a journal entry, but says nothing about retry behavior (duplicate issues), project/kanban placement, or milestone assignment that the parameters imply.

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?

A single front-loaded sentence with the primary effect first and the side effect second; efficient and easy to scan. The trailing clause "documenting the issue creation" is slightly redundant but not wasteful.

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 12-parameter tool that writes two records across two systems, the description covers only the headline behavior. It omits that the issue can be added to a project with an initial status, assigned a milestone, or that a test database can be targeted — all material for correct invocation, though the output schema eases return-value concerns.

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?

With 92% schema description coverage, the schema already documents nearly every parameter's meaning, so baseline 3 applies. The description adds no parameter-level detail such as defaults for entry_content, the meaning of use_test_db, or the interaction between project_number and initial_status.

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 states a specific verb+resource pair ("Create a GitHub issue") plus the distinctive dual effect of creating a linked journal entry, which separates it from siblings like get_github_issue or close_github_issue_with_entry. It does not, however, distinguish itself from other creation paths or clarify which repo the issue lands in.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of prerequisites (GitHub auth, repo/owner auto-detection context), and no exclusions or alternatives named. The agent must infer entirely from the schema that repo and owner can be left blank.

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