Skip to main content
Glama

Get settings

get_settings
Read-onlyIdempotent

Read the writer's main Narrareach Settings: preferences (preferredTimezone, capitalizeGeneratedNotes, writingLanguage, uiLanguage, articleLinkPlacement, articleFollowUpDelivery, and tagArticleLinksWithUtm for UTM tags on article links), the default account on each platform (Substack publication, LinkedIn destination, Instagram, and Threads, Facebook, TikTok, Pinterest and X accounts), connection health per platform, and email notification settings. Reads what Narrareach has stored; it does not refresh connections with any platform. Change preferences with update_settings. Personal account only. advisories lists anything the writer must do in Narrareach, such as resyncing Substack or resyncing LinkedIn Articles; tell the writer its message.

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": "get_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
advisoriesYes
connectionsYes
howToChangeYes
preferencesYes
notificationsYes
defaultAccountsYes
connectedAccountNo
articleConnectionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / preferences / properties / articleFollowUpDelivery
      Added value: +{
      +  "enum": [
      +    "SCHEDULE",
      +    "DRAFTS"
      +  ],
      +  "type": "string"
      +}
    • changedOutput schema / properties / preferences / required
      Previous value: -[
      -  "preferredTimezone",
      -  "capitalizeGeneratedNotes",
      -  "writingLanguage",
      -  "uiLanguage",
      -  "articleLinkPlacement",
      -  "tagArticleLinksWithUtm"
      -]New value: +[
      +  "preferredTimezone",
      +  "capitalizeGeneratedNotes",
      +  "writingLanguage",
      +  "uiLanguage",
      +  "articleLinkPlacement",
      +  "articleFollowUpDelivery",
      +  "tagArticleLinksWithUtm"
      +]
  2. Changed5 schema fields changed
    • removedOutput schema / properties / advisories / items / additionalProperties
      Removed value: -false
    • addedOutput schema / properties / advisories / items / anyOf
      Added value: +[
      +  {
      +    "additionalProperties": false,
      +    "properties": {
      +      "action": {
      +        "type": "string"
      +      },
      +      "code": {
      +        "type": "string"
      +      },
      +      "message": {
      +        "type": "string"
      +      },
      +      "platform": {
      +        "const": "SUBSTACK",
      +        "type": "string"
      +      },
      +      "requestedAt": {
      +        "format": "date-time",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "platform",
      +      "code",
      +      "message",
      +      "action",
      +      "requestedAt"
      +    ],
      +    "type": "object"
      +  },
      +  {
      +    "additionalProperties": false,
      +    "properties": {
      +      "action": {
      +        "type": "string"
      +      },
      +      "code": {
      +        "type": "string"
      +      },
      +      "message": {
      +        "type": "string"
      +      },
      +      "platform": {
      +        "const": "LINKEDIN",
      +        "type": "string"
      +      },
      +      "reason": {
      +        "enum": [
      +          "signed_out",
      +          "session_rejected"
      +        ],
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "platform",
      +      "code",
      +      "message",
      +      "action",
      +      "reason"
      +    ],
      +    "type": "object"
      +  }
      +]
    • removedOutput schema / properties / advisories / items / properties
      Removed value: -{
      -  "action": {
      -    "type": "string"
      -  },
      -  "code": {
      -    "type": "string"
      -  },
      -  "message": {
      -    "type": "string"
      -  },
      -  "platform": {
      -    "const": "SUBSTACK",
      -    "type": "string"
      -  },
      -  "requestedAt": {
      -    "format": "date-time",
      -    "type": "string"
      -  }
      -}
    • removedOutput schema / properties / advisories / items / required
      Removed value: -[
      -  "platform",
      -  "code",
      -  "message",
      -  "action",
      -  "requestedAt"
      -]
    • removedOutput schema / properties / advisories / items / type
      Removed value: -"object"
  3. Changed2 schema fields changed
    • addedOutput schema / properties / advisories
      Added value: +{
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "action": {
      +        "type": "string"
      +      },
      +      "code": {
      +        "type": "string"
      +      },
      +      "message": {
      +        "type": "string"
      +      },
      +      "platform": {
      +        "const": "SUBSTACK",
      +        "type": "string"
      +      },
      +      "requestedAt": {
      +        "format": "date-time",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "platform",
      +      "code",
      +      "message",
      +      "action",
      +      "requestedAt"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "preferences",
      -  "notifications",
      -  "defaultAccounts",
      -  "connections",
      -  "articleConnections",
      -  "howToChange"
      -]New value: +[
      +  "preferences",
      +  "notifications",
      +  "defaultAccounts",
      +  "connections",
      +  "articleConnections",
      +  "howToChange",
      +  "advisories"
      +]
  4. Changed2 schema fields changed
    • addedOutput schema / properties / preferences / properties / uiLanguage
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • changedOutput schema / properties / preferences / required
      Previous value: -[
      -  "preferredTimezone",
      -  "capitalizeGeneratedNotes",
      -  "writingLanguage",
      -  "articleLinkPlacement",
      -  "tagArticleLinksWithUtm"
      -]New value: +[
      +  "preferredTimezone",
      +  "capitalizeGeneratedNotes",
      +  "writingLanguage",
      +  "uiLanguage",
      +  "articleLinkPlacement",
      +  "tagArticleLinksWithUtm"
      +]
  5. Changed2 schema fields changed
    • addedOutput schema / properties / preferences / properties / writingLanguage
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • changedOutput schema / properties / preferences / required
      Previous value: -[
      -  "preferredTimezone",
      -  "capitalizeGeneratedNotes",
      -  "articleLinkPlacement",
      -  "tagArticleLinksWithUtm"
      -]New value: +[
      +  "preferredTimezone",
      +  "capitalizeGeneratedNotes",
      +  "writingLanguage",
      +  "articleLinkPlacement",
      +  "tagArticleLinksWithUtm"
      +]
  6. Changed1 schema field changed
    • changedOutput schema / properties / defaultAccounts / properties / linkedin / properties / defaultDestination / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": false,
      -    "properties": {
      -      "accountId": {
      -        "type": "string"
      -      },
      -      "isDefault": {
      -        "type": "boolean"
      -      },
      -      "kind": {
      -        "enum": [
      -          "profile",
      -          "page"
      -        ],
      -        "type": "string"
      -      },
      -      "label": {
      -        "type": "string"
      -      },
      -      "organizationUrn": {
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "accountId",
      -      "label",
      -      "kind",
      -      "isDefault"
      -    ],
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": false,
      +    "properties": {
      +      "accountId": {
      +        "type": "string"
      +      },
      +      "aliasAccountIds": {
      +        "items": {
      +          "type": "string"
      +        },
      +        "type": "array"
      +      },
      +      "isDefault": {
      +        "type": "boolean"
      +      },
      +      "kind": {
      +        "enum": [
      +          "profile",
      +          "page"
      +        ],
      +        "type": "string"
      +      },
      +      "label": {
      +        "type": "string"
      +      },
      +      "organizationUrn": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "accountId",
      +      "label",
      +      "kind",
      +      "isDefault"
      +    ],
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  7. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds non-obvious behavior on top: reads only stored state rather than re-polling platforms, is limited to the personal account, and surfaces actionable advisories (resyncing Substack or LinkedIn Articles). This is exactly the extra context the annotations cannot express.

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?

Front-loaded with the read scope, then constraints, then follow-up actions — a sensible order. The long parenthetical enumerating every preference key (preferredTimezone through tagArticleLinksWithUtm) is heavy and partly redundant with the output schema, but it is a single efficient block with no filler sentences.

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

Completeness5/5

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

For a zero-parameter, read-only tool with an output schema already documenting the return shape, the description supplies everything an agent still needs: what is and is not refreshed, the account scope, and how to handle advisories in the response. No gap remains that would cause a wrong invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline is 4. The description correctly adds no parameter guidance because none is needed, and the enumerated field names are payload content rather than inputs.

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?

Opens with a specific verb+resource ('Read the writer's main Narrareach Settings') and then enumerates the four content areas: preferences, default platform accounts, connection health, and email notifications. It is unmistakably distinct from the sibling mutation tool update_settings, which it names.

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

Usage Guidelines5/5

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

Explicitly routes writes to update_settings ('Change preferences with update_settings'), states the exclusion 'it does not refresh connections with any platform', and scopes the caller ('Personal account only'). It even prescribes what to do with the returned advisories ('tell the writer its message').

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources