Skip to main content
Glama

getNodeContent

Retrieve content from Adobe Experience Manager JCR nodes by specifying a path and optional depth for structured data extraction.

Instructions

Legacy: Get JCR node content

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes
depthNo

Implementation Reference

  • Core implementation of getNodeContent: fetches raw JCR node content via AEM's .json endpoint with optional depth parameter, wraps in structured response with timestamp.
    async getNodeContent(path: string, depth = 1): Promise<NodeContentResponse> {
      return safeExecute<NodeContentResponse>(async () => {
        const response = await this.httpClient.get(`${path}.json`, { 
          params: { ':depth': depth.toString() } 
        });
        
        return {
          path,
          depth,
          content: response.data,
          timestamp: new Date().toISOString()
        };
      }, 'getNodeContent');
    }
  • MCP CallToolRequestSchema handler: extracts path and depth from tool arguments, invokes AEMConnector.getNodeContent, serializes result as JSON text content.
    case 'getNodeContent': {
      const { path, depth } = args as { path: string; depth: number };
      const result = await aemConnector.getNodeContent(path, depth);
      return { content: [{ type: 'text', text: JSON.stringify(result, null, 2) }] };
  • Tool definition in MCP tools list: registers getNodeContent with description and input schema (path required string, depth optional number).
    {
      name: 'getNodeContent',
      description: 'Legacy: Get JCR node content',
      inputSchema: {
        type: 'object',
        properties: {
          path: { type: 'string' },
          depth: { type: 'number' },
        },
        required: ['path'],
      },
    },
  • TypeScript interface defining the NodeContentResponse returned by getNodeContent.
    export interface NodeContentResponse {
      path: string;
      depth: number;
      content: Record<string, unknown>;
      timestamp: string;
    }
  • Delegation method in AEMConnector that forwards to UtilityOperations.getNodeContent.
    async getNodeContent(path: string, depth?: number) {
      return this.utilityOps.getNodeContent(path, depth);
    }
Behavior1/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the action ('Get JCR node content') without detailing permissions, rate limits, output format, or side effects. For a read operation with no annotation coverage, this is insufficient.

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?

The description is brief and front-loaded with 'Legacy: Get JCR node content', which is efficient. However, it lacks necessary detail, making it under-specified rather than concise, but it avoids redundancy and is structured clearly.

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

Completeness1/5

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

Given the complexity implied by parameters and sibling tools, the description is incomplete. With no annotations, no output schema, and 0% schema coverage, it fails to provide essential context like usage scenarios, behavioral traits, or parameter details, making it inadequate for effective tool invocation.

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

Parameters1/5

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

Schema description coverage is 0%, and the description provides no information about the parameters 'path' and 'depth'. It fails to explain what these parameters mean, their expected formats, or how they affect the operation, leaving them undocumented.

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

Purpose2/5

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

The description 'Legacy: Get JCR node content' restates the tool name 'getNodeContent' with minimal elaboration, making it tautological. It specifies the resource ('JCR node content') but lacks a clear verb beyond 'Get', and doesn't differentiate from siblings like 'getPageContent' or 'getAllTextContent', leaving ambiguity about what distinguishes this tool.

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

Usage Guidelines1/5

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

No guidance is provided on when to use this tool versus alternatives. With siblings like 'getPageContent' and 'getAllTextContent', the description fails to indicate context, prerequisites, or exclusions, offering no help for an agent in selecting the appropriate tool.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/indrasishbanerjee/aem-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server